|Summary:||Inspector should support console.debug|
|Product:||WebKit||Reporter:||Adam Roben (:aroben) <aroben>|
|Component:||Web Inspector (Deprecated)||Assignee:||Adam Roben (:aroben) <aroben>|
|Version:||528+ (Nightly build)|
|Bug Depends on:|
Description Adam Roben (:aroben) 2008-05-20 16:14:10 PDT
The Inspector should support console.debug for Firebug parity.
Comment 1 Adam Roben (:aroben) 2008-05-20 16:22:50 PDT
*** Bug 19154 has been marked as a duplicate of this bug. ***
Comment 3 Adam Roben (:aroben) 2008-05-20 17:58:44 PDT
Created attachment 21265 [details] patch v1 + ChangeLog
Comment 4 Sam Weinig 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.
Comment 5 Adam Roben (:aroben) 2008-05-21 09:20:00 PDT
Created attachment 21268 [details] patch v2 + ChangeLog Addresses Sam's comments
Comment 7 Alex Yaroshevich 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?