Closed Bug 832917 Opened 11 years ago Closed 10 years ago

Visiting an UTF-16 page adds an UTF-16 item to the Character Encoding menu that persists even upon navigating to a non-UTF-16 page

Categories

(Firefox for Android Graveyard :: General, defect)

defect
Not set
normal

Tracking

(firefox29 fixed, firefox30 fixed, firefox31 fixed)

RESOLVED FIXED
Firefox 31
Tracking Status
firefox29 --- fixed
firefox30 --- fixed
firefox31 --- fixed

People

(Reporter: hsivonen, Assigned: Margaret)

Details

(Whiteboard: [fixed by bug 943262])

Steps to reproduce:
 1) Enable the Character Encoding menu in settings.
 2) Navigate to http://hsivonen.iki.fi/test/moz/never-show-user-supplied-content-as-utf-16.htm
 3) Open the Character Encoding menu.
 4) Close the Character Encoding menu.
 5) Navigate to http://hsivonen.iki.fi/test/moz/
 6) Open the Character Encoding menu.

Actual results:
At step #6, an option labeled "UTF-16" appears in the menu.

Expected results:
Expected "UTF-16", "UTF-16LE" and "UTF-16BE" to be blacklisted so that they never appear in the menu. (You can visit http://hsivonen.iki.fi/test/moz/charset-menu/child-6-meta-parent-bomless-utf-16-child-with-http.htm16be instead of the first page in the steps to reproduce to see "UTF-16BE" stick around in the menu.)

Additional info:
Bug 832910 is about disabling the menu on UTF-16 pages (among others), so you can’t perform step #3. Still, it would be best to blacklist "UTF-16", "UTF-16LE" and "UTF-16BE" just in case. (They are already blacklisted on desktop.)
This was fixed as a side effect of fixing bug 943262.
Assignee: nobody → margaret.leibovic
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 943262]
Target Milestone: --- → Firefox 31
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.