Firefox/Features/Plugin keyboard focus: Difference between revisions

m
no edit summary
m (clearing in prep for migration to new feature page format)
mNo edit summary
Line 1: Line 1:
{{FeatureStatus
|Feature name=Plugin keyboard focus
|Feature stage=Definition
|Feature health=OK
|Feature status note=Josh is working on bug 637253 in preparation for the real fix.
}}
{{FeatureTeam
|Feature feature manager=Alex Limi
|Feature lead engineer=Josh Aas
|Feature qa lead=AndreiD
|Feature ux lead=Alex Limi
}}
{{FeaturePageBody
|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 ux design=Interaction is described in {{bug|491141}}.
|Feature implementation notes={{Bug|491141}}, {{bug|637253}}
}}
{{FeatureInfo
|Feature priority=P1
|Feature roadmap=User Experience
|Feature list=Platform
|Feature engineering team=Platform
}}
{{FeatureTeamStatus
|Feature products status=tbd
|Feature engineering status=tbd
|Feature security status=tbd
|Feature privacy status=tbd
|Feature localization status=tbd
|Feature accessibility status=tbd
|Feature qa status=tbd
|Feature ux status=tbd
}}
canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906

edits