Move featuregate title to features.ftl used by about:preferences and about:support; and other strings to genai.ftl. Allow prompts to use l10nId to get fluent attributes. Convert inline strings for menu and shortcuts to fluent. Update simplify, add explain prompts.
Differential Revision: https://phabricator.services.mozilla.com/D218279
This was the feature flag behind which the settings page's 'search' functionality was written.
It's been there for years now, and it is high time to clean this up.
Differential Revision: https://phabricator.services.mozilla.com/D217034
Co-author/investigator: Tim Giles <tgiles@mozilla.com>
Delay sychronous loading of ESM based custom elements until the
DOMContentLoaded event. With D212190--which this patch depends on--the
components that have already been used on the page will be synchronously
loaded when customElements.setElementCreationCallback is registered.
Differential Revision: https://phabricator.services.mozilla.com/D212191
Thanks to mhowell for the STRIP_ANCHOR function in the Fluent migration.
We were using the "for" attribute on a XUL label which does not behave
like an HTML label. This prevented the programmatic association
between the checkbox and the label. By utilizing moz-label, we maintain
the accesskey behavior of the previous XUL label.
Additionally we use moz-support-link to remove the
"collection-backlogged-crash-reports-link" Fluent string.
Differential Revision: https://phabricator.services.mozilla.com/D204557
Note that this does not expose the about:translations localization file
since that is a developer-focused view that's not ready or planned for
general usage.
Differential Revision: https://phabricator.services.mozilla.com/D179360
Note that this does not expose the about:translations localization file
since that is a developer-focused view that's not ready or planned for
general usage.
Differential Revision: https://phabricator.services.mozilla.com/D179360
It occurred to me that we're not actually using `toggle-button.css` anywhere since the about:preferences work landed. I definitely should have removed the reference in `preferences.xhtml` as part of that patch, whoops.
Differential Revision: https://phabricator.services.mozilla.com/D169530
This patch changes the Firefox Suggest preference toggles to use the new `moz-toggle` element.
For testing purposes, set `browser.urlbar.quicksuggest.enabled` to `true` to make the toggles visible in `about:preferences#privacy`.
Differential Revision: https://phabricator.services.mozilla.com/D167881
I also renamed migration-dialog.[js|html|css] to migration-dialog-window.[js|html|css] to
make it clearer that those resources are for when the wizard is being shown in a separate
window. I also updated the documentation to reflect this.
Differential Revision: https://phabricator.services.mozilla.com/D169014
A new FTL file for the extension is added under `browser/preferences/` rather than `browser/extensions/formautofill/`, as the former is a more common location for FTL localizations, and the extension already relies on an FTL file hosted outside its own directory, `toolkit/payments/payments.ftl`.
The dialogs are not fully migrated in this patch, as some of the strings are shared with the edit dialogs and are migrated separately.
A Fluent migration for the localization changes applied here is included in the next patch after this one.
Differential Revision: https://phabricator.services.mozilla.com/D155478
A new FTL file for the extension is added under `browser/preferences/` rather than `browser/extensions/formautofill/`, as the former is a more common location for FTL localizations, and the extension already relies on an FTL file hosted outside its own directory, `toolkit/payments/payments.ftl`.
The dialogs are not fully migrated in this patch, as some of the strings are shared with the edit dialogs and are migrated separately.
A Fluent migration for the localization changes applied here is included in the next patch after this one.
Differential Revision: https://phabricator.services.mozilla.com/D155478
These changes replicate the exact appearance and behaviour of `<label is="text-link">`. There are a few possible enhancements not tackled here, as this is the simplest possible migration implementation:
* We could switch to using `button` elements in this case, based on the styling and the fact that the `addonsButton` has some additional behaviour on top of navigation. This would necessitate re-working the current style rules a bit.
* Somewhat relatedly, we could change the `helpButton` and `about:policies` anchor elements to always switch tabs if the link has already been clicked/opened, rather than always opening in a new tab
Differential Revision: https://phabricator.services.mozilla.com/D144624
