DevTools/Features/ConsoleObjectCompletion
Status
| Console Object Completion | |
| Stage | Complete |
| Status | Complete |
| Release target | Firefox 10 |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Console Object Completion
|Feature stage=Complete |Feature status=Complete |Feature version=Firefox 10 |Feature health=OK |Feature status note=` }}
Team
| Product manager | Kevin Dangoor |
| Directly Responsible Individual | Kevin Dangoor |
| Lead engineer | Panos Astithas |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Vlad Maniac (irc:vladmaniac) |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Kevin Dangoor
|Feature feature manager=Kevin Dangoor |Feature lead engineer=Panos Astithas |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Vlad Maniac (irc:vladmaniac) |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
This feature tracks work that was originally blended into the WebConsole7 feature, but not completed for Firefox 7.
When the Web Console shipped with Firefox 4, it provided the first console object to be always available to content in Firefox. It provided enough of the console object to be useful (console.log being by far the most popular method on the object). However, it was still lacking in features that developers commonly use.
2. Users & use cases
You can open up the Web Console and type console.dir(window) and see a set of properties and values from the window object in the console object.
In a JavaScript program, you can use console.group and console.groupEnd to visually group together related log messages.
3. Dependencies
`
4. Requirements
- The console object implements the portion of the API that is implemented by both Firebug and WebKit. Notably, this includes time, timeEnd, dir, group and groupEnd.
Non-goals
`
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
`
Operations review
`
Stage 4: Development
9. Implementation
- bug 658368 for time/timeEnd (needs sr+)
- bug 664131 for group/groupEnd (needs r+)
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=This feature tracks work that was originally blended into the WebConsole7 feature, but not completed for Firefox 7.
When the Web Console shipped with Firefox 4, it provided the first console object to be always available to content in Firefox. It provided enough of the console object to be useful (console.log being by far the most popular method on the object). However, it was still lacking in features that developers commonly use. |Feature users and use cases=You can open up the Web Console and type console.dir(window) and see a set of properties and values from the window object in the console object.
In a JavaScript program, you can use console.group and console.groupEnd to visually group together related log messages. |Feature dependencies=` |Feature requirements=* The console object implements the portion of the API that is implemented by both Firebug and WebKit. Notably, this includes time, timeEnd, dir, group and groupEnd. |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=* bug 658368 for time/timeEnd (needs sr+)
- bug 664131 for group/groupEnd (needs r+)
|Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Developer Tools |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | DevTools |
{{#set:Feature priority=P1
|Feature rank=999 |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 | Signed off | 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=Signed off |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=` }}