Empty list shown in "Text Encoding" and "Web Developer" options
Categories
(Firefox :: Menus, defect)
Tracking
()
People
(Reporter: Srik_Wanar, Unassigned)
References
Details
Attachments
(1 file)
|
123.84 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
Click to open the application menu, then select More->Text Encoding or Web Developer
Actual results:
It shows an empty list.
When I create a new profile, the "Text Encoding" option totally disappears, and "Web Developer" becomes "More Tools" which may have slightly different set of submenus.
Expected results:
A list of text encodings and tools should be shown.
It works fine in nightly 91.0a1 (2021-06-03) (64-bit), and degenerates in the 06-04's build.
Comment 1•5 years ago
|
||
You mention a new profile, but a new profile doesn't have a "Text Encoding" or a "Web Developer" menu.
Given that the menu in your screenshot has icons, that's not the Proton UI. Did you disable Proton from about:config?
I can reproduce on 90.0b3 and 91.0a1(2021-06-05) BuildID 20210605211222 after setting browser.proton.enabled to false and then restarting Firefox.
Comment 3•5 years ago
|
||
Given that flag is supposed to be removed in 91, I assume this would make this bug a WONTFIX.
| Reporter | ||
Comment 4•5 years ago
|
||
(In reply to Francesco Lodolo [:flod] from comment #3)
Given that flag is supposed to be removed in 91, I assume this would make this bug a WONTFIX.
In the old profile, the menu remains unchanged when I toggled the browser.proton.enabled switch.
I see that the new UI won't have "Text Encoding" menu, then how can I change the page encoding in new versions?
(In reply to Srik Wanar from comment #4)
In the old profile, the menu remains unchanged when I toggled the
browser.proton.enabledswitch.
I see that the new UI won't have "Text Encoding" menu, then how can I change the page encoding in new versions?
I think some proton prefs don't take full effect until you restart the browser.
As for the Text Encoding menu in Proton, you might want to watch bug 1702914 and/or bug 1706566.
Comment 6•5 years ago
|
||
Sounds like there isn't a bug actually here. I'll close this as invalid.
Description
•