DevTools/Features/ConsoleQueuedMessages
Status
| Console Queued Message Display | |
| Stage | Complete |
| Status | In progress |
| Release target | Firefox 12 |
| Health | OK |
| Status note | Currently available in Nightly. |
{{#set:Feature name=Console Queued Message Display
|Feature stage=Complete |Feature status=In progress |Feature version=Firefox 12 |Feature health=OK |Feature status note=Currently available in Nightly. }}
Team
| Product manager | Kevin Dangoor |
| Directly Responsible Individual | Dave Camp |
| Lead engineer | Mihai Sucan |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Vlad Maniac (irc: vladmaniac, #automation) |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | David Dahl |
{{#set:Feature product manager=Kevin Dangoor
|Feature feature manager=Dave Camp |Feature lead engineer=Mihai Sucan |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Vlad Maniac (irc: vladmaniac, #automation) |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=David Dahl }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
If a user's JavaScript logs messages using console.log 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 without needing to reload the page.
This feature also works for JavaScript errors and is very convenient for developers.
2. Users & use cases
With code like console.log("hi"); 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.
3. Dependencies
`
4. Requirements
- messages logged using console.* methods should be displayed on open of Web Console (subject to limitations to avoid a queue that's too large)
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.
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
in progress
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=If a user's JavaScript logs messages using console.log 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 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 console.log("hi"); 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 dependencies=` |Feature requirements=* messages logged using console.* 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 functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=in progress |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 6 |
| Theme / Goal | ` |
| Roadmap | Developer Tools |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | DevTools |
{{#set:Feature priority=P1
|Feature rank=6 |Feature theme=` |Feature roadmap=Developer Tools |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=DevTools }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | sec-review-needed | dchan |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | Test Plan |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-needed |Feature security health=Assigned |Feature security notes=dchan |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=Test Plan |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}