Closed
Bug 1376102
Opened 7 years ago
Closed 1 year ago
[hamburger menu] Text Encoding menu should honor browser.menu.showCharacterEncoding setting
Categories
(Firefox :: Menus, defect, P4)
Firefox
Menus
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dao, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [reserve-photon-structure])
Text Encoding should probably be in the Web Developer menu, and with browser.menu.showCharacterEncoding=true it should probably be a top-level item. The current location in the More menu doesn't serve either use case very well.
Reporter | ||
Updated•7 years ago
|
Whiteboard: [photon-structure][triage]
Comment 1•7 years ago
|
||
This is technically a regression, but it doesn't seem like a severe one purely for putting the menu behind 1 more click than it would be otherwise. We created this pref ~7 years ago (bug 596173) and bug 598516 comment 3 shows that even 4 years ago usage of the menu was basically non-existent. There is also the mitigating factor that, since bug 596173 landed, there is now a customizable toolbar item that users who need this regularly could just put directly into their toolbar. Unless other information surfaces as part of answering bug 1375464 comment 4, I think this can go into the reserve rather than MVP.
Keywords: regression
Whiteboard: [photon-structure][triage] → [reserve-photon-structure]
Updated•7 years ago
|
Flags: qe-verify?
Priority: -- → P3
Updated•7 years ago
|
Flags: qe-verify? → qe-verify+
Updated•7 years ago
|
QA Contact: gwimberly
Updated•7 years ago
|
Priority: P3 → P4
Updated•2 years ago
|
Severity: normal → S3
Comment 2•1 year ago
|
||
Is it ok to close this now that the text encoding menu has been replaced with the repair text encoding button ?
Flags: needinfo?(dao+bmo)
Comment 3•1 year ago
|
||
I think so, yes.
Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(dao+bmo)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•