I do this as much as possible. However the Firefox in-page translation software seems to do something that actually changes the page (and this can break things like forms) whereas chromium browsers do some kind of translation layer on top, so the page can run normally beneath it.
It’s an infuriating reason but right now it means I have to split my browser use depending on if I need translations or not.
I do this as much as possible. However the Firefox in-page translation software seems to do something that actually changes the page (and this can break things like forms) whereas chromium browsers do some kind of translation layer on top, so the page can run normally beneath it.
It’s an infuriating reason but right now it means I have to split my browser use depending on if I need translations or not.
Is that new in the last couple years or so? I recall chrome breaking form entry left and right when translating before i could read the language.
Right now chromium is my best choice for translations in-page
I used to keep it installed just for that too so I’m not judging. I just also recall forms being broken by the translate tool.
Yeah I think it’s something about breaking the attributes of html elements. If it translates some id or data value then the form can’t find it.
The same for if it replaces elements or otherwise breaks hooks and event listeners.
You know you can install the “chromium-like” translation thing on Firefox as well, as an extension? E.g. this: https://addons.mozilla.org/en-US/firefox/addon/traduzir-paginas-web/