We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Character Encoding Menu unresponsive

  • 2 Antworten
  • 4 haben dieses Problem
  • 2 Aufrufe
  • Letzte Antwort von 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.

Ausgewählte Lösung

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.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (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

Ausgewählte Lösung

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.