Closed Bug 769186 Opened 11 years ago Closed 11 years ago
[devtb] Decide on a key sequence for the developer toolbar
No description provided.
This patch reflects what I'd like to do, the correct thing to do is under discussion. Bug 768150 to pref the toolbar on by default removes the key sequence to avoid a clash with the editor.
We previously removed the key sequence until we could find one that didn't clash. We found ctrl+shift+/
(In reply to Joe Walker from comment #2) > We previously removed the key sequence until we could find one that didn't > clash. We found ctrl+shift+/ Hmm. At least for German users like me and probably other locales this might be a choice as bad as Panorama's next/prev group shortcut. I need to press shift to reach '/' so this effectively overrides the add-on bar toggle, or doesn't work at all and toggles the add-on bar, not sure.
Comment on attachment 639186 [details] [diff] [review] v2 "/" happens to be shift+7 with a German keyboard layout and I think shift+: with a French one, making accel+shift+/ inaccessible. We usually keep command keys consistent across locales, and even if we made an exception, I think we could count on localizers getting this wrong. In this case I don't think we should make an exception anyway, as I don't think it's unreasonable for the keyboard layout to divert from what Firefox locales would expect.
Attachment #639186 - Flags: review?(ttaubert) → review-
I'm not sure that we really need a keyboard shortcut for the add-on bar; stealing that might be an option. Ironically, it was added for "users who heavily rely on add-ons for certain task modes (e.g. *web development*)" (bug 616015, emphasis mine).
There aren't good answers to this problem, but I agree that this doesn't work for anyone with a German keyboard. The developer tools use ctrl+shift/alt+cmd as their modifiers, and there are no free letters without crashing something, I've previously given up on punctuation, for l10n reasons and have done so again, function keys don't work properly on Mac, and numbers are really confusing because we English can't even agree amongst *ourselves* what should be on top of 2. Or 3. I'm currently trying to work out a way to use ctrl+shift+v (again), and to resolve the conflict with paste-without-formatting in a contenteditable. The UX part of this decision is being done in consultation with shorlander/bdils.
This update does 2 things: - It changes the key sequence to shift+F2 - It leaves the menu item as a toggle, but makes the keyboard shortcut a 'focus' shortcut, which takes you to the command line even when the toolbar is already open.
Bug ping, I'd love to get this into 16 if possible. Thanks.
Attachment #639493 - Flags: review?(ttaubert) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.