Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Avatar for Username

Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

Character Encoding Menu unresponsive

  • 2 vastausta
  • 4 henkilöllä on sama ongelma
  • 11 näyttöä
  • Viimeisin kirjoittaja AaronMT

Kazenoryu
Kazenoryu
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.

Valittu ratkaisu

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.

Lue tämä vastaus kontekstissaan 👍 0

Kaikki vastaukset (2)

AaronMT
AaronMT
more options

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

AaronMT
AaronMT
more options

Valittu ratkaisu

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.