Proton appmenu "Settings" is internally inconsistent with Firefox > Preferences on macOS
Categories
(Firefox :: Menus, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox88 | --- | affected |
People
(Reporter: yoasif, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: nightly-community, ux-consistency)
Steps to reproduce:
- Set
browser.proton.enabled
to true - Restart Firefox
- Click app menu
- Click Firefox menu
What happens:
Observe that the labels are different in two places but go to the same place (about:preferences
).
Expected result:
Preferences is used widely on macOS - Settings is more of a Windows-ism. Preferences should be the copy in both places.
Reporter | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
:yoasif, if you think that's a regression, could you try to find a regression range using for example mozregression?
Comment 2•4 years ago
|
||
(In reply to Asif Youssuff from comment #0)
Preferences is used widely on macOS - Settings is more of a Windows-ism. Preferences should be the copy in both places.
It's not a Windows-ism (historically Windows uses Options, IIRC only Windows 10 has Settings), and there are bugs currently fixing other labels.
I assume this makes it a WONTFIX, but leaving the final decision to triagers.
Reporter | ||
Comment 3•4 years ago
|
||
(In reply to Francesco Lodolo [:flod] from comment #2)
It's not a Windows-ism (historically Windows uses Options, IIRC only Windows 10 has Settings), and there are bugs currently fixing other labels.
Well, it is newly a Windows-ism. :) That was a throwaway comment though - ultimately, it is out of place in macOS and also internally inconsistent.
Comment 4•4 years ago
|
||
I don't understand why this got marked as a regression from bug 1695671 - the landing of that bug postdates the filing of this bug, and also fixed the issue raised in the summary of this bug, by making the two labels consistent.
Comment 5•4 years ago
|
||
We're reversing course on "Settings" specifically for the macOS menubar. That work is happening in bug 1698550.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Description
•