Firefox/Features/Plugin keyboard focus
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. I believe 637253 is resolved fixed. Can we move into the larger fix here now? I'm also very very interested in whether or not there are any short-term hacks we can deploy to alleviate this problem sooner rather than later. |
{{#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.
I believe 637253 is resolved fixed. Can we move into the larger fix here now? I'm also very very interested in whether or not there are any short-term hacks we can deploy to alleviate this problem sooner rather than later. }}
Team
| Product manager | Asa Dotzler |
| Directly Responsible Individual | Asa Dotzler |
| Lead engineer | Josh Aas |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Paul Silaghi |
| UX lead | Alex Limi |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=Asa Dotzler |Feature lead engineer=Josh Aas |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Paul Silaghi |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
bug 491141, bug 637253 — is there any way we could do what's described in bug 692973
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 — is there any way we could do what's described in bug 692973 |Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 10 |
| Theme / Goal | ` |
| Roadmap | User Experience |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | Flash |
| Engineering team | Plugins |
{{#set:Feature priority=P1
|Feature rank=10 |Feature theme=` |Feature roadmap=User Experience |Feature secondary roadmap=` |Feature list=Desktop |Feature project=Flash |Feature engineering team=Plugins }}
Team status notes
| status | notes | |
| Products | ` | After talking with Accessibility and UX, it's clear that we need to move this up in priority. |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=After talking with Accessibility and UX, it's clear that we need to move this up in priority. |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=` }}