Firefox/Features/Plugin keyboard focus: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
|Feature overview=When a plugin is focused (typically Flash), it will steal keyboard shortcuts, so you can't do thing like open a new tab or close the tab without unfocusing the plugin container. We should give plugins the ability to pass through shortcuts to the browser. | |Feature overview=When a plugin is focused (typically Flash), it will steal keyboard shortcuts, so you can't do thing like open a new tab or close the tab without unfocusing the plugin container. We should give plugins the ability to pass through shortcuts to the browser. | ||
This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.) | This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.) | ||
|Feature ux design=Interaction is described in {{bug|491141}}. | |Feature ux design=Interaction is described in {{bug|491141}}. | ||
|Feature implementation notes={{Bug|491141}}, {{bug|637253}} | |Feature implementation notes={{Bug|491141}}, {{bug|637253}} | ||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||
|Feature priority= | |Feature priority=P2 | ||
|Feature rank=10 | |||
|Feature roadmap=User Experience | |Feature roadmap=User Experience | ||
|Feature list= | |Feature list=Desktop | ||
|Feature engineering team=Platform | |Feature engineering team=Platform | ||
}} | }} | ||
{{FeatureTeamStatus}} | {{FeatureTeamStatus}} | ||
Revision as of 16:50, 30 August 2011
Status
| Plugin keyboard focus | |
| Stage | Definition |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | Josh is working on bug 637253 in preparation for the real fix. |
{{#set:Feature name=Plugin keyboard focus
|Feature stage=Definition |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Josh is working on bug 637253 in preparation for the real fix. }}
Team
| Product manager | Asa Dotzler |
| Directly Responsible Individual | Alex Limi |
| Lead engineer | Josh Aas |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | AndreiD |
| UX lead | Alex Limi |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=Alex Limi |Feature lead engineer=Josh Aas |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=AndreiD |Feature ux lead=Alex Limi |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
- I'd like to make sure that if the developer of the plugin content hasn't explicitly said that they'll override Ctrl/Cmd-qualified shortcuts, they'll be passed through by default.
Stage 1: Definition
1. Feature overview
When a plugin is focused (typically Flash), it will steal keyboard shortcuts, so you can't do thing like open a new tab or close the tab without unfocusing the plugin container. We should give plugins the ability to pass through shortcuts to the browser.
This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.)
2. Users & use cases
`
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
Interaction is described in bug 491141.
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=* I'd like to make sure that if the developer of the plugin content hasn't explicitly said that they'll override Ctrl/Cmd-qualified shortcuts, they'll be passed through by default. |Feature overview=When a plugin is focused (typically Flash), it will steal keyboard shortcuts, so you can't do thing like open a new tab or close the tab without unfocusing the plugin container. We should give plugins the ability to pass through shortcuts to the browser.
This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.) |Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=Interaction is described in bug 491141. |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 491141, bug 637253 |Feature landing criteria=` }}
Feature details
| Priority | P2 |
| Rank | 10 |
| Theme / Goal | ` |
| Roadmap | User Experience |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | Platform |
{{#set:Feature priority=P2
|Feature rank=10 |Feature theme=` |Feature roadmap=User Experience |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=Platform }}
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=` }}