1875232 - Firefox Translate often makes websites unusable

Status: RESOLVED DUPLICATE of bug 1837424

(Firefox :: Translations, defect)

Description

[Alex Leonard]

Attachment: kda88cc0iH.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0

Steps to reproduce:

Here is just the most recent example

Visit: https://www.myhermes.de/service/kontakt/?wt_cc1=kundenservice&wt_mc=re_zn19 with auto translate from German to English

Select Theme "Receiving"
Select Concerns "Where is my show?" (mistranslation)
Click Continue

Actual results:

Steps 3 and 4 appear but Step 2 is entirely missing

Expected results:

Step 2 should be displayed as the form validation prevents submission without Step 2 being filled out.

However this is just a tiny indication of how often Firefox inline webpage translation renders a website completely non-functional. I was super excited that translation was added, but I often find myself having to open Chrome or Edge to get inline translation that works without breaking forms or other elements on a page. Often I find large elements disappear, or hover/dropdown menus no longer appear once the page has been translated.

Additionally, form elements are often broken with date dropdowns completely broken, or form validation messed up. The biggest issue with form submission issues is that when you decide to turn off inline translation using "Show Original" - the entire page does a full reload - resulting in you likely losing everything you entered thus far in the form.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Translation' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Monica Chiorean]

I was able to reproduce the issue on Win10x64 using Firefox build 121.0. If translation is not performed step2 is displayed, but if translated step2 is missing.
Marking as new.

Comment 3

[Greg Tatum [:gregtatum] (REO Fx132)]

This is fixed by Bug 1837424. I reproduced in 121 but not 122 on macOS. Luckily 122 is released next week.