[meta] Migrate strings from toolkit/chrome/global/datetimebox.dtd to Fluent
Categories
(Core :: Layout: Form Controls, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: nordzilla, Assigned: eemeli)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
Attachments
(1 file)
As part of the M3 milestone, we should migrate strings from toolkit/chrome/global/datetimebox.dtd
to Fluent
At the time of creating this bug, this file contains 17 strings that should be migrated to Fluent.
These strings don't block the startup path or anything else critical, but should be moved eventually.
This will serve as a meta bug for the migration.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Startup and Profile System' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Updated•3 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
As the widget requires the individual fields' placeholder values to
be known during their build, the DOMLocalization instance used here
needs to have sync methods enabled. For the same reason, the
placeholder strings need to be separate messages, rather than
attributes on the same message as the corresponding label.
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Migrating the strings to use DOM Localization effectively ends up meaning that either bug 1761893 or bug 1730431 needs to be fixed first. The former looks likelier to land soon, so marked that as a blocker for this.
Updated•2 years ago
|
Pushed by earo@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/35362dccb42a Migrate datetimebox strings from DTD to FTL. r=emilio,fluent-reviewers,flod
Comment 5•2 years ago
|
||
bugherder |
Description
•