Bug 19153 - Inspector should support console.debug
: Inspector should support console.debug
Status: RESOLVED FIXED
: WebKit
Web Inspector (Deprecated)
: 528+ (Nightly build)
: All All
: P2 Enhancement
Assigned To:
:
: InRadar
:
: 14354
  Show dependency treegraph
 
Reported: 2008-05-20 16:14 PST by
Modified: 2011-03-10 11:53 PST (History)


Attachments
patch v1 + ChangeLog (3.62 KB, patch)
2008-05-20 17:58 PST, Adam Roben (:aroben)
sam: review-
Review Patch | Details | Formatted Diff | Diff
patch v2 + ChangeLog (5.12 KB, patch)
2008-05-21 09:20 PST, Adam Roben (:aroben)
timothy: review+
Review Patch | Details | Formatted Diff | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-05-20 16:14:10 PST
The Inspector should support console.debug for Firebug parity.
------- Comment #1 From 2008-05-20 16:22:50 PST -------
*** Bug 19154 has been marked as a duplicate of this bug. ***
------- Comment #2 From 2008-05-20 16:22:59 PST -------
<rdar://problem/5950856>
------- Comment #3 From 2008-05-20 17:58:44 PST -------
Created an attachment (id=21265) [details]
patch v1 + ChangeLog
------- Comment #4 From 2008-05-20 18:20:06 PST -------
(From update of attachment 21265 [details])
The aliasing should be done in Console, not JSConsole.  The JS wrapper is supposed to be a thin wrapper that knows as little as possible about the implementation.
------- Comment #5 From 2008-05-21 09:20:00 PST -------
Created an attachment (id=21268) [details]
patch v2 + ChangeLog

Addresses Sam's comments
------- Comment #6 From 2008-05-21 22:59:49 PST -------
Committed in r34010
------- Comment #7 From 2011-03-10 11:53:02 PST -------
DevTools in Chrome have console-debug-level style class, but console.debug creates div with console-log-level.
console.info method exists but also with class console-log-level.
They're really different messages. Why they creates with the same class?