Customizable Hotkeys (new Firefox feature, needs SUMO article)
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: kbryant, Assigned: ffloare)
Details
Attachments
(1 file)
|
96.70 KB,
image/png
|
Details |
top of the customizable hotkeys prototype UI
Did you check out the steps and FAQs for submitting requests to the CX content team? [REQUIRED]
YES
Content access restriction: Is the content restricted to staff or under embargo? [REQUIRED]
NO
Product [REQUIRED]
Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)
Select the type of request [REQUIRED]
KB content update/ new content
Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]
New SUMO article needed for new feature: MVP for customizable hotkeys (a.k.a, keyboard shortcuts, shortcuts).
MVP scope
- Working functional prototype, unpolished UI/UX; looks and behaves like Firefox’s more “hidden” about: pages (e.g., about:config, about:cache, about:license, about:support)
- UI opens in Firefox by typing about:keyboard in search bar
- Desktop only: Windows, Mac, Linux
- Keyboard: QWERTY English US (Other keyboard users can still try it, but we expect they’ll find bugs.)
- Locale: global
- Accessibility: WCAG2.2 compliant, but also aiming for delightful
Users want customizable hotkeys so they can:
- Replace shortcuts that are hard or impossible for them to press (e.g., too many keys, too far apart, can’t reach row)
- Replace complex, hard-to-remember shortcuts with easier ones
- Transfer an existing Firefox shortcut to a different action in our list (e.g., never use it for the assigned purpose, need it for something they use more frequently)
- Eliminate shortcut conflicts between Firefox and other software (e.g., same shortcut is used by an add-on, the OS, assistive technology software)
Additional background
The first Bugzilla request for this feature was filed 25 years ago and ~50 more have been filed since. Customizable Hotkeys consistently stays in the top 5 Connect ideas and has more than 1,470 votes. Some users said they would switch entirely to Firefox if this feature were available, while new Firefox users noted that lack of keyboard shortcut customization is a key pain point. Many commenters highlighted that a few competitors like Vivaldi and Opera offer this feature, and its absence is a major barrier to adopting Firefox.
Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
Production -- Customizable Hotkeys will ride the trains to Release
Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]
Full rollout, to everyone
Please indicate if this is an on- or off-train release [REQUIRED]
On train release -- currently targeting 147 (pending full engineering review and bug fixes).
Worst case scenario: 149
What is the anticipated release date? [REQUIRED]
Release for 147 = Jan 13
Does the content need to be published prior to the release date? If so, when? [REQUIRED]
It would helpful to have this in Nightly 147 (Nov 10 - Dec 4), but we won't need it until we publicly announce it via Connect.
Date for public announcement has not yet been set, but we wanted to get this ticket in now so we can start working on a draft with y'all.
Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]
Shipping to all languages.
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]
- https://bugzilla.mozilla.org/show_bug.cgi?id=1635774
- Full Project Brief
- please let me know if you want/need a meeting to see the working prototype and ask questions (as a visually impaired person, it's challenging for me to record a demo, and recording a Zoom meeting has been a helpful option for everyone in the past)
Please include links to any design assets, visuals, figma files, etc. [REQUIRED]
This project has no UX/Designer -- none were available and we were able to produce an accessible text-based UI without one. (We will definitely require one for v2).
Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]
Functional Spec (from Project Brief)
Does the content need approval before publishing? If yes, identify the one approver responsible for this task.
Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]
YES -- Kim Bryant
|
||
Comment 1•2 months ago
|
||
Asana: https://app.asana.com/1/90589597529/project/1203460865189761/task/1211761439310122?focus=true
|
Assignee | |
Comment 2•2 months ago
|
||
I have written a first draft here: https://docs.google.com/document/d/1-YkBt_dLpVvRiQdB9dsdpEEIm8ZRJlt30EB5Lpsrm_E/edit?tab=t.0
Please review it, and let me know if you have any suggestions. Thank you.
Hi, Flavius! I haven't forgotten this -- we've discovered issues via QA that will require updates to the article, and I'm waiting to make edits until we work through a last few bugs. I'm currently planning to pick this up late this week or early next week.
(In reply to Flavius Floare from comment #2)
I have written a first draft here: https://docs.google.com/document/d/1-YkBt_dLpVvRiQdB9dsdpEEIm8ZRJlt30EB5Lpsrm_E/edit?tab=t.0
Please review it, and let me know if you have any suggestions. Thank you.
Hi, Flavius!
I finally have an answer on how to proceed with this. I will update the article this week to reflect the current "proof of concept/MVP" UI and functionality.
However: we'd like to publish it very early on Tue, Jan 27 (before 8am ET) to align with a formal kickoff to gather user research that will inform what we build for V2. (Both folks who worked on the project will be back in the office on that date, and thus better able to quickly respond to incoming feedback.)
Can you please advise on whether there are additional steps I need to take to make sure it launches on Tue, Jan 27? Thank you!
Description
•