Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Character Encoding Menu unresponsive

  • 2 respostas
  • 4 têm este problema
  • 8 visualizações
  • Última resposta por 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.

Solução escolhida

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.

Ler esta resposta no contexto 👍 0

Todas as respostas (2)

more options

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

more options

Solução escolhida

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.