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.
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.
Whiteboard: [photon-structure][triage] → [reserve-photon-structure]
You need to log in before you can comment on or make changes to this bug.