Confirmed users, Bureaucrats and Sysops emeriti
2,974
edits
Firefox/Features/Plugin keyboard focus: Difference between revisions
Jump to navigation
Jump to search
m
Firefox/Features/Plugin keyboard focus (view source)
Revision as of 21:42, 29 July 2011
, 29 July 2011no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 6: | Line 6: | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Asa Dotzler | |||
|Feature feature manager=Alex Limi | |Feature feature manager=Alex Limi | ||
|Feature lead engineer=Josh Aas | |Feature lead engineer=Josh Aas | ||
| Line 14: | Line 15: | ||
|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 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. | |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 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}} | ||