Bugzilla

Currently, [Infobar CTAs](https://searchfox.org/mozilla-central/source/browser/components/asrouter/modules/InfoBar.sys.mjs#64) are not RemoteL10n configurable. This means that we cannot use localized string ids that did not exist in the fx we're targeting served with [ms-lang-pack](https://github.com/mozilla-services/ms-language-packs?tab=readme-ov-file#messaging-system-language-packs-for-remote-settings) through Remote Settings. This was problematic with the RootCA initiative, as we wanted to use new strings that were not available.

Aside from the RootCa initiative, there is no immediate use case however it could potentially future proof Infobars and other messaging in the event we need to target older fx.

There may be other [messaging components](https://searchfox.org/mozilla-central/search?q=lazy%5C.RemoteL10n%5C.(formatLocalizableText%7CcreateElement)&path=&case=false&regexp=true) that need to be hooked up as well

Currently, [Infobar CTAs](https://searchfox.org/mozilla-central/source/browser/components/asrouter/modules/InfoBar.sys.mjs#64) are not RemoteL10n configurable. This means that we cannot use localized string ids that did not exist in the fx we're targeting served with [ms-lang-pack](https://github.com/mozilla-services/ms-language-packs?tab=readme-ov-file#messaging-system-language-packs-for-remote-settings) through Remote Settings. This was problematic with the RootCA initiative, as we wanted to use new strings that were not available.

Aside from the RootCa initiative, there is no immediate use case however it could potentially future proof Infobars and other messaging in the event we need to target older fx builds with newer localized strings.

There may be other [messaging components](https://searchfox.org/mozilla-central/search?q=lazy%5C.RemoteL10n%5C.(formatLocalizableText%7CcreateElement)&path=&case=false&regexp=true) that need to be hooked up as well