Changing the translation language for specific pages intermittently doesn't perform translation
Categories
(Firefox :: Translations, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox125 | --- | wontfix |
firefox126 | --- | wontfix |
firefox127 | --- | fix-optional |
People
(Reporter: marco, Unassigned)
References
(Regression)
Details
(Keywords: regression)
STR:
- Open https://www.turkiye.gov.tr/turk-kizilay-en-yakin-kan-bagis-merkezi
- Translate from Turkish to Italian
- Change the target language from Italian to English and click "Translate"
Sometimes the page is translated to English, sometimes it is just shown in the original language.
It doesn't work most of the times I try on https://www.turkiye.gov.tr/turk-kizilay-en-yakin-kan-bagis-merkezi, but sometimes it works, which makes me think this is a race condition.
Reporter | ||
Comment 1•7 months ago
|
||
I can also reproduce this on https://www.bild.de/.
Comment 2•7 months ago
|
||
The severity field is not set for this bug.
:gregtatum, could you have a look please?
For more information, please visit BugBot documentation.
Comment 3•7 months ago
|
||
This kind of feels like an S2 to me.
Comment 4•7 months ago
•
|
||
I narrowed this down in mozregression to this patch stack:
Then I bisected it locally to this commit:
https://phabricator.services.mozilla.com/D190727
Greg, I'm sure you could have guessed that it was an issue in that section of the code, but the nice thing is that it has been broken since November 5, 2023 (Nightly). Given that we haven't had a bug report for this until now (and from Marco, at that), I would guess that there's a mixture this being this race condition that may be somewhat specific to particular site conditions (e.g. switching active languages on Wikipedia continues to work fine), and that changing the active translation language isn't as common of a situation as translating once.
Comment 5•7 months ago
|
||
Setting Regressed by
field after analyzing regression range found by mozregression in comment #4.
Comment 6•7 months ago
|
||
Set release status flags based on info from the regressing bug 1815339
Updated•7 months ago
|
Comment 7•7 months ago
|
||
Evengy pinging as Triage Owner. Since this has an S2 severity, was wondering what the priority is on getting this fixed?
Next week is the final week of beta for Fx126, if not fixed in time could we expect something for Fx127 at least?
(uplift to Fx1266 would depend on the fix)
Reporter | ||
Comment 8•7 months ago
|
||
I would suggest lowering severity to S3 given what Erik said in comment 4.
Updated•7 months ago
|
Updated•7 months ago
|
Comment 9•7 months ago
|
||
:gregtatum, since you are the author of the regressor, bug 1815339, could you take a look?
For more information, please visit BugBot documentation.
Updated•6 months ago
|
Description
•