Migrate stub installer to Fluent
Categories
(Firefox :: Installer, task, P3)
Tracking
()
People
(Reporter: molly, Unassigned)
References
(Blocks 1 open bug)
Details
See bug 1596812 comment 30 and below.
[I don't know if there's a Fluent-related metabug somewhere that this should be under; if so feel free to add it there]
|
Reporter | |
Comment 1•5 years ago
|
||
[picking up from bug 1596812 comment 33]
I didn't know about fluent-compiler, that sounds like a really nice idea for this, but it does output an ES6 module, which could not be used directly in the stub's IE8 web view, and I'm not very excited about the idea of adding some kind of JS bundler or transpiler to that build.
Once again, not all the localized strings in the stub installer go through the new web UI. There is still a lot of NSIS logic in there and some of those strings are used only from there. Therefore, anything that involves JavaScript is an incomplete solution and something else would also have to be done to cover the rest. That's why I'm trying to avoid using any Fluent DOM stuff at all, so that we don't need two separate pipelines for just a handful of strings.
|
||
Comment 2•5 years ago
|
||
(In reply to Molly Howell (she/her) [:mhowell] from comment #0)
[I don't know if there's a Fluent-related metabug somewhere that this should be under; if so feel free to add it there]
Looks like most Fluent bugs block bug 1581212.
|
||
Comment 3•5 years ago
|
||
I'll leave it up to Zibi to declare the right tracker.
I could see us having success with an NSIS plugin based on fluent.rs. Though I wouldn't know how hard or easy that was.
|
||
Comment 4•5 years ago
|
||
Yeah, we could use fluent-rs! But even migrating the ones in JS to Fluent would be helpful to keep reducing the scope of .properties in the product.
Description
•