canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,093
edits
DevTools/Features/ConsoleQueuedMessages: Difference between revisions
DevTools/Features/ConsoleQueuedMessages (view source)
Revision as of 13:44, 30 August 2012
, 30 August 2012no edit summary
No edit summary |
No edit summary |
||
| (11 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=Console Queued Message Display | |Feature name=Console Queued Message Display | ||
|Feature stage= | |Feature stage=Complete | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature version=Firefox | |Feature version=Firefox 12 | ||
|Feature health= | |Feature health=OK | ||
|Feature status note= | |Feature status note=Currently available in Nightly. | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Kevin Dangoor | |Feature product manager=Kevin Dangoor | ||
|Feature feature manager= | |Feature feature manager=Dave Camp | ||
|Feature lead engineer= | |Feature lead engineer=Mihai Sucan | ||
|Feature additional members= | |Feature qa lead=Vlad Maniac (irc: vladmaniac, #automation) | ||
|Feature additional members=David Dahl | |||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature overview=If a user's JavaScript logs messages using <tt>console.log</tt> and similar methods ''before'' the Web Console has been opened, those messages are lost. In order to see that log output, the user needs to reload the page. | |Feature overview=If a user's JavaScript logs messages using <tt>console.log</tt> and similar methods ''before'' the Web Console has been opened, those messages are lost. In order to see that log output, the user needs to reload the page. | ||
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 without needing to reload the page. | ||
This feature also works for JavaScript errors and is very convenient for developers. | |||
|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 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. | |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. | ||
|Feature qa review=in progress | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||
|Feature priority=P1 | |Feature priority=P1 | ||
|Feature rank=6 | |||
|Feature roadmap=Developer Tools | |Feature roadmap=Developer Tools | ||
|Feature list=Desktop | |Feature list=Desktop | ||
|Feature engineering team=DevTools | |Feature engineering team=DevTools | ||
}} | }} | ||
{{FeatureTeamStatus}} | {{FeatureTeamStatus | ||
|Feature security status=sec-review-needed | |||
|Feature security health=Assigned | |||
|Feature security notes=dchan | |||
|Feature qa notes=[[/Test_Plan|Test Plan]] | |||
}} | |||