WNP fallback evergreen is not displayed for a couple of locales
Categories
(www.mozilla.org :: Bedrock, defect)
Tracking
(firefox84 verified)
Tracking | Status | |
---|---|---|
firefox84 | --- | verified |
People
(Reporter: cgeorgiu, Assigned: agibson)
References
Details
Attachments
(1 obsolete file)
Affected versions
- RC 84.0
Affected platforms
- Windows 10 x64
- macOS 10.15
- Ubuntu 18.04 x64
Prerequisites
- Have one of the following Fx locale builds downloaded: fa, bs, af.
Steps to reproduce
- Change the update channel to
release-localtest
, from the channel-prefs.js file. - Update Firefox to its latest version.
- Observe the WNP displayed.
Expected result
- WNP evergreen fallback is displayed, e.g. https://www.mozilla.org/de/firefox/100.0/whatsnew/all/
Actual result
- WNP promoting VPN is displayed, e.g. https://user-images.githubusercontent.com/1461798/95471150-99a92e80-094f-11eb-8184-3e68d954c9ca.png
Suggested Severity
- S3 since only a couple of locales are affected, and they are not the most used ones.
Regression range
- N/A
Additional details
- In the case of "af" locale, it seems that the update link from URL bar, points to en-GB.
Comment 1•4 years ago
|
||
It turns out the evergreen WNP is not actually available in all locales
supported by Firefox Desktop.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Great catch, Bedrock issue here: https://github.com/mozilla/bedrock/issues/9769
Assignee | ||
Comment 3•4 years ago
|
||
Fixed in issue linked above:
https://www.mozilla.org/fa/firefox/84.0/whatsnew/all/
https://www.mozilla.org/bs/firefox/84.0/whatsnew/all/
https://www.mozilla.org/af/firefox/84.0/whatsnew/all/
Updated•4 years ago
|
Reporter | ||
Comment 4•4 years ago
•
|
||
We've managed to confirm that the WNP fallback is displayed upon update to 84.0RC2, for the locales from comment 3.
I'm not sure if this is a problem with WNP itself, looks more like a localization issue. The fallback page is displayed in english for those locales. Is this expected, can you please let us know, Justin?
Comment 5•4 years ago
|
||
Yes, that's expected.
Background: These locales were never "activated" on www.mozilla.org, because they never met any threshold for localized content. In this new approach to whatsnew pages, we've activated them and they'll see content in en-US until they are localized. The l10n team will try to enroll new localizers to help get those pages localized.
Updated•4 years ago
|
Reporter | ||
Comment 6•4 years ago
|
||
Thanks for the explanations. I'll mark this as verified fixed, since we did not encounter again the problem, when testing on localtest, cdn and release update channels.
Description
•