Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Firefox built-in translator ignores the translate="no" attribute

  • 1 resposta
  • 0 tem este problema
  • 11 visualizações
  • Última resposta de TyDraniu

more options

My website has some web components that render an icon based on their icon attribute, like so: <button-icon icon="close" translate="no" type="button" variant="standard"></button-icon>

everything works fine until i translate the page using the latest firefox 133 on both windows 11 and android, the icon rendered in the shadow dom gets translated by firefox ignoring the translate="no" and the icon in the button doesn't show correctly anymore. This doesn't happen when i translate the webpage using chrome. If I remove the translate="no" attribute, i get the same error in chrome too, and that's the reason i added the translate attribute. I believe this isn't intended behaviour and i would consider this a bug, and tbh makes me wanna use firefox less because if I translate automatically then not only my website breaks but also many other have the same risk. If translate="no" is applied to a web component, firefox should avoid translating elements in its shadow dom. I hope this pain point can be addressed in future versions, let me know if i can provide more information, thanks for reading and have a nice day.

My website has some web components that render an icon based on their icon attribute, like so: <button-icon icon="close" translate="no" type="button" variant="standard"></button-icon> everything works fine until i translate the page using the latest firefox 133 on both windows 11 and android, the icon rendered in the shadow dom gets translated by firefox ignoring the translate="no" and the icon in the button doesn't show correctly anymore. This doesn't happen when i translate the webpage using chrome. If I remove the translate="no" attribute, i get the same error in chrome too, and that's the reason i added the translate attribute. I believe this isn't intended behaviour and i would consider this a bug, and tbh makes me wanna use firefox less because if I translate automatically then not only my website breaks but also many other have the same risk. If translate="no" is applied to a web component, firefox should avoid translating elements in its shadow dom. I hope this pain point can be addressed in future versions, let me know if i can provide more information, thanks for reading and have a nice day.

Todas as respostas (1)

more options

Generally we support "class=notranslate" and translate="no" so it definitely looks like a bug. Can you report it on https://bugzilla.mozilla.org ? Thanks.

Útil?

Faça uma pergunta

É necessário entrar na sua conta para responder a publicações. Faça uma nova pergunta, se ainda não tiver uma conta.