Closed
Bug 1221493
Opened 10 years ago
Closed 10 years ago
Upgrading from FF43 to FF44 shows an old whatsnew page in French
Categories
(www.mozilla.org :: Pages & Content, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: pbro, Unassigned)
References
Details
Attachments
(2 files)
(Sorry, I'm not sure where to file this).
I have my dev-edition Firefox set to French, and I just restarted it now to have the new 44 release.
After restart, the what's new page appeared, and it pointed to this URL:
https://www.mozilla.org/fr/firefox/44.0a2/whatsnew/?oldversion=43.0a2
I'll attach a screenshot of what this page contains, but basically, it shows information about the perf tools, which is something we released in the past.
FF44 is supposed to be mostly about Creative Tools (animation tools) and the DevToolsChallenger demo. But I'm not seeing those on the FR page.
If I go to https://www.mozilla.org/en-US/firefox/44.0a2/whatsnew/?oldversion=43.0a2
Then I see the correct content (I'll attach a screenshot too).
Reporter | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
Cory, do you know what's going on here? Those URLs look fine, so somehow the page content is not correct? Did it just not get localized in time or something?
Also pinging Axel in case he can shed light on the l10n situation here.
Blocks: 1196530
Severity: normal → major
Component: General → Pages & Content
Flags: needinfo?(l10n)
Flags: needinfo?(cprice)
Product: Firefox → www.mozilla.org
Version: unspecified → Production
Comment 3•10 years ago
|
||
That's expected, given that Developer Edition copy and content becomes available barely days before release instead of weeks like the rest of the Campaign content.
If we want to fix this, we need to change that on the other side, not l10n.
The strings were pushed out this morning, only a couple of locales translated them.
https://www.mozilla.org/de/firefox/44.0a2/whatsnew/?oldversion=43.0a2
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(l10n)
Flags: needinfo?(cprice)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•