Firefox/Features/Plugin keyboard focus: Difference between revisions

Jump to navigation Jump to search
m
no edit summary
mNo edit summary
mNo edit summary
Line 13: Line 13:
{{FeaturePageBody
{{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 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.
|Feature ux design=Interaction is described in {{bug|491141}}.
|Feature ux design=Interaction is described in {{bug|491141}}.
Line 24: Line 23:
|Feature engineering team=Platform
|Feature engineering team=Platform
}}
}}
{{FeatureTeamStatus
{{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

Navigation menu