New issue
Advanced search Search tips

Issue 657700 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 617178
Owner: ----
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

debug() is completely disabled when it is already defined

Project Member Reported by phistuck@gmail.com, Oct 20 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36

Steps to reproduce the problem:
1. Go to -
data:text/html,<!doctype html><div id=debug><script>function stuff() { }; setInterval(stuff, 500);</script>
Or to -
data:text/html,<!doctype html><script>var debug; function stuff() { }; setInterval(stuff, 500);</script>
2. Open the Developer Tools.
3. Enter in the console -
debug(stuff);

What is the expected behavior?
A breakpoint is hit.

What went wrong?
An exception (it is not a function).

Did this work before? No 

Chrome version: 54.0.2840.59  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

I guess this should just be added to the console namespace.
console.debugFunction (and in the future, console.debugProperty), since console.debug is already taken.
 

Comment 1 by phistuck@gmail.com, Oct 20 2016

Probably the same with monitor(), monitorEvents and any other command line API not under the console namespace.
Mergedinto: 617178
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment