Closed Bug 1911760 Opened 2 years ago Closed 2 years ago

mozintl: "skr" is incorrectly defined in region() instead of language() set

Categories

(Core :: Internationalization: Localization, defect)

Firefox 128
defect

Tracking

()

VERIFIED FIXED
131 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- fixed
firefox129 --- wontfix
firefox130 --- fixed
firefox131 --- fixed

People

(Reporter: henry-x, Assigned: flod)

References

(Regression)

Details

(Keywords: regression)

Attachments

(3 files)

Bug 1899905 added skr to the availableLocaleDisplayNames.region but did not add a corresponding entry in regionNames.ftl. So getRegionDisplayNames will give a fluent error for missing region-name-skr.

Was it meant to be added to availableLocaleDisplayNames.language instead?

:bolsson, since you are the author of the regressor, bug 1899905, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(bolsson)

Thanks for catching, that's indeed an error.

So getRegionDisplayNames will give a fluent error for missing region-name-skr.

I haven't been able to trigger this error. When do you see it?

Assignee: nobody → francesco.lodolo
Flags: needinfo?(bolsson)
Attachment #9417896 - Attachment description: Bug 1911760 - Move skr from regions to languages set in mozIntl, r=eemeli → Bug 1911760 - Move skr from region to language set in mozIntl, r=eemeli
Summary: Missing region-name-skr in regionNames.ftl → mozintl: "skr" is incorrectly defined in region() instead of language() set
Pushed by flodolo@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/58322f347f7f Move skr from region to language set in mozIntl, r=eemeli

I haven't been able to trigger this error. When do you see it?

It comes from Tor Browser. When a user is having trouble connecting to tor due to censorship, they can select their region to find them a suitable tor bridge. We basically do the following:

const codes = Services.intl.getAvailableLocaleDisplayNames("region");
const names = Services.intl.getRegionDisplayNames(undefined, codes);

With ESR 128 we started getting the fluent error message.

I'll wait for this to land, test it, and then request uplift to beta and ESR128.

Set release status flags based on info from the regressing bug 1899905

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 131 Branch

Verified on Nightly Saraiki build (20240806211239), the language name is now displayed correctly in the accept-languages dialog.

Status: RESOLVED → VERIFIED
Attachment #9418059 - Flags: approval-mozilla-beta?
Attachment #9418061 - Flags: approval-mozilla-esr128?

beta Uplift Approval Request

  • User impact if declined: Users of Saraiki (skr) builds will see the language displayed as [skr] in the accept-languages dialog.
  • Code covered by automated testing: no
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: No
  • Risk associated with taking this patch: None
  • Explanation of risk level: skr was incorrectly defined in the set of regions instead of languages.
  • String changes made/needed: None
  • Is Android affected?: no

esr128 Uplift Approval Request

  • User impact if declined: Users of Saraiki (skr) builds will see the language displayed as [skr] in the accept-languages dialog. This is also triggering a warning in Web Console for Tor Browser, which is based on ESR branches.
  • Code covered by automated testing: no
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: -
  • Risk associated with taking this patch: None
  • Explanation of risk level: skr was incorrectly defined in the set of regions instead of languages.
  • String changes made/needed: None
  • Is Android affected?: no
Attachment #9418059 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Attachment #9418061 - Flags: approval-mozilla-esr128? → approval-mozilla-esr128+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: