Closed
Bug 1485002
Opened 6 years ago
Closed 5 years ago
[META] Fluent migration using in-tree strings
Categories
(Firefox :: New Tab Page, enhancement, P1)
Firefox
New Tab Page
Tracking
()
RESOLVED
FIXED
People
(Reporter: k88hudson, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
Attachments
(1 file)
96 bytes,
text/x-google-doc
|
Details |
No description provided.
Comment 1•6 years ago
|
||
Just noting that in bug 1508409 comment 2, release management has raised concerns of the late string uplift to beta that is required with the current prerendered string export process. Seems like this meta bug with bug 1485004 ftl prerendering might help.
Although there might need to be an additional bug to get things working with language repacks ??
See Also: → 1508409
Comment 2•6 years ago
|
||
I believe the current intent of "Fluent migration" is to also get rid of strings-import
step and directly use strings from resource:///localization
basically finishing the transition to l10n-central started in bug 1457223 which got rid of the strings-export
step.
Summary: [META] Fluent migration → [META] Fluent migration using in-tree strings
Comment 3•6 years ago
|
||
To be explicit, removing strings-import
means regular l10n updates to browser/locales/l10n-changesets.json
result in new tab getting the new strings without needing an export containing the newly imported strings.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Priority: -- → P1
Updated•5 years ago
|
No longer blocks: bugzy-epic
Updated•5 years ago
|
Blocks: pocket-newtab
Assignee | ||
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
Comment 4•5 years ago
|
||
Comment 5•5 years ago
|
||
Feature landed in Firefox 69
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•