Chrome Inspection
Status
| Chrome Inspection | |
| Stage | Draft |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | This is an initial draft of this feature, requirements are subject to modification. |
{{#set:Feature name=Chrome Inspection
|Feature stage=Draft |Feature status=` |Feature version=` |Feature health=OK |Feature status note=This is an initial draft of this feature, requirements are subject to modification. }}
Team
| Product manager | Daniel Buchner |
| Directly Responsible Individual | Daniel Buchner |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Daniel Buchner
|Feature feature manager=Daniel Buchner |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
In order to serve the add-on inspection use-case, we need to extend current UI inspection tools to target the chrome elements of the browser. This will likely result in a shift in presentation of the inspector's current UI when the user chooses to inspect chrome.
The current wrap-web-content UI of the inspector suggests to users an inability to select elements outside of its element bounds. Some form of detached inspector UI that shows the user a clear connection to the chrome inspection context may be a good option for showing the clear difference between the two inspection scenarios.
2. Users & use cases
Nearly all add-ons with front-facing UI would immediately benefit. In the process of serving the add-ons developer case with this enhancement, we would provide to Firefox developers a significantly more usable answer to Firefox chrome inspection than the current tool, DOM Inspector. This would have obvious organizational efficiency benefits that will help drive development our core product.
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
Add mock showing use of the inspection feature a in detached, chrome-targeted version of current dev tools.
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
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=In order to serve the add-on inspection use-case, we need to extend current UI inspection tools to target the chrome elements of the browser. This will likely result in a shift in presentation of the inspector's current UI when the user chooses to inspect chrome.
The current wrap-web-content UI of the inspector suggests to users an inability to select elements outside of its element bounds. Some form of detached inspector UI that shows the user a clear connection to the chrome inspection context may be a good option for showing the clear difference between the two inspection scenarios. |Feature users and use cases=Nearly all add-ons with front-facing UI would immediately benefit. In the process of serving the add-ons developer case with this enhancement, we would provide to Firefox developers a significantly more usable answer to Firefox chrome inspection than the current tool, DOM Inspector. This would have obvious organizational efficiency benefits that will help drive development our core product. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=Add mock showing use of the inspection feature a in detached, chrome-targeted version of current dev tools. |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Developer Tools |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | DevTools |
{{#set:Feature priority=Unprioritized
|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 | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}