canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,093
edits
DevTools/Features/ConsoleQueuedMessages: Difference between revisions
Jump to navigation
Jump to search
DevTools/Features/ConsoleQueuedMessages (view source)
Revision as of 14:57, 21 July 2011
, 21 July 2011no edit summary
(Created page with "{{FeatureStatus |Feature name=Console Queued Message Display |Feature stage=Development |Feature status=In progress |Feature version=Firefox 8 |Feature health=OK }} {{FeatureTeam...") |
No edit summary |
||
| Line 16: | Line 16: | ||
With this feature in place, the user will see those messages as soon as they open the Web Console. | With this feature in place, the user will see those messages as soon as they open the Web Console. | ||
|Feature users and use cases=With code like <tt>console.log("hi");</tt> in a JS file, you should be able to load the page with the Web Console closed, open the Web Console and see "hi" in the log. | |Feature users and use cases=With code like <tt>console.log("hi");</tt> in a JS file, you should be able to load the page with the Web Console closed, open the Web Console and see "hi" in the log. | ||
|Feature requirements=* messages logged using <tt>console.*</tt> methods should be displayed on open of Web Console (subject to limitations to avoid a queue that's too large) | |||
|Feature non-goals=* Ideally, CSS and JavaScript errors would also be stored but if we can't get that on the first pass, that's acceptable. | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||