Bug 14263 - Safari's existing console.log does not log into the Web Inspector's console
Summary: Safari's existing console.log does not log into the Web Inspector's console
Status: RESOLVED DUPLICATE of bug 14953
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 523.x (Safari 3)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://www.getfirebug.com/console.html
Keywords:
Depends on:
Blocks: 14354
  Show dependency treegraph
 
Reported: 2007-06-20 22:41 PDT by Niels Leenheer (HTML5test)
Modified: 2007-12-05 14:12 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Niels Leenheer (HTML5test) 2007-06-20 22:41:50 PDT
When using Firebug you can use the console object to log debug information to the javascript console. 

For example:

console.log('debug information');

We could use the same API for a similar purpose.
Comment 1 Matt Lilek 2007-06-20 23:46:33 PDT
Personally, I think we should go beyond that and basically replace the javascript console from the debug menu and integrate that into the inspector
Comment 2 Timothy Hatcher 2007-06-21 00:02:11 PDT
Yes, we plan to make console.log work with the new inspector.
Comment 3 Niels Leenheer (HTML5test) 2007-06-21 00:04:42 PDT
Matt: yes. 

In case my original description was not clear enough. I was talking about the console of the Web Inspector. Not the old Javascript console that can be enabled in the Debug menu.

If you manually log messages they should appear in the Web Inspector console.
Comment 4 Timothy Hatcher 2007-06-24 11:36:31 PDT
Bug 14354 is about supporting the entire Firebug console API. This bug should be about just getting console.log moved.
Comment 5 Timothy Hatcher 2007-06-24 11:37:27 PDT
Bug 14354 is about supporting the entire Firebug console API. This bug should be about just getting console.log moved.
Comment 6 David Kilzer (:ddkilzer) 2007-08-12 16:29:06 PDT
See also Bug 14953.

Comment 7 Timothy Hatcher 2007-12-05 14:12:47 PST
This was fixed by bug 14953. Marking this as a dupe.

*** This bug has been marked as a duplicate of 14953 ***