custom-avatar-alt was changed without a new ID, causing failure in l10n infra
Categories
(Toolkit :: Startup and Profile System, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox-esr140 | --- | unaffected |
firefox140 | --- | unaffected |
firefox141 | --- | unaffected |
firefox142 | --- | fixed |
People
(Reporter: flod, Assigned: tbersentes)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-profile-management])
Attachments
(1 file)
https://phabricator.services.mozilla.com/D252385
This changed
custom-avatar-alt =
.alt = Custom avatar
To
custom-avatar-alt = Custom
My local instance of Pontoon committed just this
custom-avatar-alt =
Luckily only Italian was affected so far, but this means that quarantine is blocked.
The string ID needs to be changed (that's this bug). But there's a bug in our infrastructure, because Pontoon shouldn't have committed that translation in the first place.
@eemeli
Can you file a separate bug in the right place? Not sure if Pontoon or moz-l10n. Apparently Pontoon is in a state where it only knows about the string's version with alt
attribute, even a forced sync won't change that.
Revert link: https://hg.mozilla.org/integration/autoland/rev/e4a1f24183370c53e6e9d937f4d3dd5ba064ad74
Failure log: https://treeherder.mozilla.org/logviewer?job_id=517742526&repo=autoland
Comment 1•1 month ago
|
||
Set release status flags based on info from the regressing bug 1966951
Reporter | ||
Updated•1 month ago
|
Reporter | ||
Updated•1 month ago
|
Comment 2•1 month ago
|
||
For moz.l10n, https://github.com/mozilla/moz-l10n/pull/91 should fix its part of the issue, as such an empty message should be serialized as
custom-avatar-alt = { "" }
to make it valid Fluent.
I'm keeping the needinfo on, as at least some work is required in Pontoon as well.
Comment 3•1 month ago
|
||
It looks like Pontoon will need an update once the moz.l10n PR lands and a new release is available. Regarding its general behaviour in a case like this, I added pontoon#3718. The related oddity in the firefox-l10n-source scripts ought to get cleared up by updating its moz.l10n dependency to its latest version.
Hey :eemeli, do we need to update the strings that surfaced this bug?
Comment 5•1 month ago
|
||
Yes, for two reasons:
- I'm pretty sure that it was a mistake for
custom-avatar-alt
to not have its value in the.alt
attribute. All of the other*-avatar-alt
strings use an.alt
attribute, and it's used as thel10n-id
of an<img>
element, which ought not have any contents. - The string content changes from "Custom avatar" to "Avatar", so the message ought to have a new l10n id like
custom-avatar-alt-2
.
Assignee | ||
Updated•1 month ago
|
Thanks, we're on it.
Assignee | ||
Comment 7•1 month ago
|
||
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•23 days ago
|
Description
•