Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

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

Learn More

In-message anchors are forced to open in a web browser

  • 3 respostas
  • 3 têm este problema
  • 1 visualização
  • Última resposta por SadFirefoxUser

more options

In Thunderbird 31, when I click on a link in a message that points to an anchor within the same message (e.g. imap://account@mail.server.net:143/fetch%3EUID%3E.INBOX%3E55326#1) it pops open a Firefox window to open the message instead of scrolling through the message pane to the anchor. This used to work properly in previous versions.

Am I missing a setting somewhere, is it a bug, or is it the new normal?

Thanks, --James

In Thunderbird 31, when I click on a link in a message that points to an anchor within the same message (e.g. imap://account@mail.server.net:143/fetch%3EUID%3E.INBOX%3E55326#1) it pops open a Firefox window to open the message instead of scrolling through the message pane to the anchor. This used to work properly in previous versions. Am I missing a setting somewhere, is it a bug, or is it the new normal? Thanks, --James

Solução escolhida

This is probably Bug 974857 - Anchor links not working when reading HTML e-mails (involving IMAP)

Ler esta resposta no contexto 👍 0

Todas as respostas (3)

more options

Solução escolhida

This is probably Bug 974857 - Anchor links not working when reading HTML e-mails (involving IMAP)

more options

That's it exactly!

Thanks for pointing me in the right direction.

--James

more options

Sorry, but I did not understand the solution, or if there even is a solution! Did I miss something or is this still a bug awaiting a future solution? The forum entry speaks of 'chosen solution'--very confusing...