Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Character Encoding Menu unresponsive

  • 2 wotmołwje
  • 4 maja tutón problem
  • 2 napohladaj
  • Poslednja wotmołwa wot 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.

Wubrane rozrisanje

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.

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (2)

more options

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

more options

Wubrane rozrisanje

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.