Align quick actions cmd keywords better with displayed actions
Categories
(Firefox :: Address Bar, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox-esr102 | --- | unaffected |
firefox103 | --- | unaffected |
firefox104 | --- | unaffected |
firefox105 | --- | affected |
People
(Reporter: aflorinescu, Unassigned)
References
(Blocks 1 open bug)
Details
Given the current quick actions keywords, there are cases in which we are not in the category: you get what you see, in the sense that a View Downloads will not be listed when you'd expect it to show under a "view" and users are not privy to the cmd-keywords, so they shouldn't need to build muscle memory and be something more natural than not.
For sure quick actions search-mode should function more like a filter than a match in the addressbar (bug 1783881), but still, feels like we should aim for a better ballance betwen the displayed action and the keywords triggering it.
I'm a bit reluctant to list hard examples, since I understand that having a "view" keyword would end up with address bar actions spam, but I also feel like some actions display names are too explicit, for example, so this would reduce the need to have so many hits on a view or open input if set as keywords:
- Open Settings -> Settings
- Open Downloads -> Downloads
- Open Private Browsing Window -> Private Window
- Take a Screenshot -> Take screenshot (take as a keyword) or Screenshot
- Open Inspector -> Inspector
- ...
Comment 1•2 years ago
|
||
The strings are being reviewed by product and going to be updated in https://bugzilla.mozilla.org/show_bug.cgi?id=1783153 and the filtering will happen in 1783881 so this seems like a dupe between those?
Reporter | ||
Comment 2•2 years ago
|
||
(In reply to Dale Harvey (:daleharvey) from comment #1)
The strings are being reviewed by product and going to be updated in https://bugzilla.mozilla.org/show_bug.cgi?id=1783153 and the filtering will happen in 1783881 so this seems like a dupe between those?
Sure, we can dupe it and refer to bug 1783153/UX doc for further changes/verification.
Description
•