RESOLVED FIXED 19153
Inspector should support console.debug 
https://bugs.webkit.org/show_bug.cgi?id=19153
Summary Inspector should support console.debug
Adam Roben (:aroben)
Reported 2008-05-20 16:14:10 PDT
The Inspector should support console.debug for Firebug parity.
Attachments
patch v1 + ChangeLog (3.62 KB, patch)
2008-05-20 17:58 PDT, Adam Roben (:aroben) 		sam: review-
DetailsFormatted DiffDiff
patch v2 + ChangeLog (5.12 KB, patch)
2008-05-21 09:20 PDT, Adam Roben (:aroben) 		timothy: review+
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Adam Roben (:aroben)
Comment 1 2008-05-20 16:22:50 PDT
*** Bug 19154 has been marked as a duplicate of this bug. ***
Mark Rowe (bdash)
Comment 2 2008-05-20 16:22:59 PDT
<rdar://problem/5950856>
Adam Roben (:aroben)
Comment 3 2008-05-20 17:58:44 PDT
Created attachment 21265 [details] patch v1 + ChangeLog
Sam Weinig
Comment 4 2008-05-20 18:20:06 PDT
Comment on attachment 21265 [details] patch v1 + ChangeLog 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.
Adam Roben (:aroben)
Comment 5 2008-05-21 09:20:00 PDT
Created attachment 21268 [details] patch v2 + ChangeLog Addresses Sam's comments
Adam Roben (:aroben)
Comment 6 2008-05-21 22:59:49 PDT
Committed in r34010
Alex Yaroshevich
Comment 7 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?
Note You need to log in before you can comment on or make changes to this bug.