Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Character Encoding Menu unresponsive

  • 2 antwoorden
  • 4 hebben dit probleem
  • 2 weergaven
  • Laatste antwoord van AaronMT

more options

I've updated the app today to the newest version. When I tried changing the character encoding on a website that'S not displaying properly, I found that selecting a different encoding did nothing except check the circle next to it. The only thing I could do from there was to select cancel or push return on my phone. It's getting a bit annoying to surf on a few websites now since I can't fix the encoding.

I've updated the app today to the newest version. When I tried changing the character encoding on a website that'S not displaying properly, I found that selecting a different encoding did nothing except check the circle next to it. The only thing I could do from there was to select cancel or push return on my phone. It's getting a bit annoying to surf on a few websites now since I can't fix the encoding.

Gekozen oplossing

I filed bug https://bugzilla.mozilla.org/show_bug.cgi?id=1003897

It looks like this is fixed on Firefox 30. As a work-around, you might be interested in installing Firefox Beta off of Google Play tomorrow when we update it. It will be Firefox 30.

Dit antwoord in context lezen 👍 0

Alle antwoorden (2)

more options

Thanks for the report. Looks like this slipped in for Firefox 29 unfortunately. I will file a bug.

more options

Gekozen oplossing

I filed bug https://bugzilla.mozilla.org/show_bug.cgi?id=1003897

It looks like this is fixed on Firefox 30. As a work-around, you might be interested in installing Firefox Beta off of Google Play tomorrow when we update it. It will be Firefox 30.