VisualEditor does not respect custom accesskey accelerator key
Open, NormalPublic1 Story Points


Neither VisualEditor nor the 2017 wikitext editor honors Firefox’s ui.key.contentAccess preference. For example, I set it so that Control-F focuses the search box instead of Control-Option-F. This preference works with any accesskey in MediaWiki, including the Save button in the old wikitext editor, but not the Save button in VisualEditor. Instead, VisualEditor’s Save button responds only to Control-Option-S, which would be the standard key binding on macOS and the default in Firefox. This is admittedly an edge case, but I customize the accelerator because I find any Control-Option combination to be awkward to type.

mxn created this task.Apr 6 2017, 7:03 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 6 2017, 7:03 AM
DLynch added a subscriber: DLynch.Apr 10 2017, 4:35 PM

I think there's not any way for us to tell what you've set this property to, so I don't think we can adapt to it.

mxn added a comment.Apr 10 2017, 5:27 PM

Yeah, I think the only way to respect the setting would be to use the accesskey HTML attribute or DOM property, as most of MediaWiki does. (Manually binding to hardcoded key combinations using event listeners would lead to this issue, for example.)

OOjs UI buttons support the 'accessKey' config option these days. In the past they didn't, back when the VisualEditor project started.

Jdforrester-WMF set the point value for this task to 1.
Jdforrester-WMF triaged this task as Normal priority.
Jdforrester-WMF moved this task from To Triage to TR1: Releases on the VisualEditor board.