Also remove public access to the internal Localization instance
and update the call in CustomizableWidgets to not detach the method.
Differential Revision: https://phabricator.services.mozilla.com/D178049
The l10n migration shows a diff for `addon-downloading-and-verifying`,
`addon-confirm-install-message`, and `addon-confirm-install-unsigned-message`
due to the en-US source having `1` rather than `one` variants.
For `addon-confirm-install-some-unsigned-message`,
the en-US source has a single-variant plural selector for localization to new languages.
In addition to moving strings from `browser.properties` to the new `addonNotifications.ftl`,
there's some shuffling of strings to & from `browser.ftl` as well.
The intent is to collect the more rarely used strings out of files loaded during startup,
especially as many of the notification strings need to be formatted in a sync context.
For the most part, string keys are left roughly the same as they were in .properties.
With some guidance, some rationalisation might make sense as a part of this for the
rather wide selection of prefixes in this set:
- `addon-`
- `site-permission-install-`
- `webext-`
- `xpinstall-`
The `addon-install-started` and `addon-install-failed` notifications appear to need sync l10n formatting,
as using async format calls before their `PopupNotifications.show()` leads to test failures in
`toolkit/mozapps/extensions/test/xpinstall/browser_doorhanger_installs.js`.
Differential Revision: https://phabricator.services.mozilla.com/D178235
This changes the arguments of `ExtensionData.formatPermissionStrings()`.
The second `bundle` arg is dropped, and a `localization` option is added.
Call sites in m-c are updated, but this will also need a matching update for Thunderbird.
A few Thunderbird test cases will also need to be updated,
as they currently point to a non-existing localization file paths
"messenger/addons.ftl" and "messenger/addonPermissions.ftl".
As discussed at the addon workweek,
the Fluent l10n keys for extension permissions match the pattern:
webext-perms-description-{name}
where `{name}` is the permission's sanitized name.
A fluent-lint exception is added for the capitalization of these generated names.
To allow for message updates and subsequent l10n identifier updates,
a `PERMISSION_L10N_ID_OVERRIDES` map is provided.
Because Fluent localization keys are not enumerable
and attempting to format a missing key is an error,
the `PERMISSIONS_WITH_MESSAGE` set must be kept in sync with message updates.
Differential Revision: https://phabricator.services.mozilla.com/D158663
When rustc generates its dependency file, it takes into account current
version of the codebase. If an update of the code then happens, with,
say an ipdl file being removed, the corresponding .h is no longer
generated and make rightfully complains about missing dependency.
Allow this kind of transition by providing a dummy rule for each
dependency generated by rustc.
Differential Revision: https://phabricator.services.mozilla.com/D178617
This was papered over because WPT used to default to stylo_threads = 1 :'(
This hits in /mathml/presentation-markup/scripts/subsup-2.html and some
other tests when getting font metrics, but we actually are fine just
calling it off the main thread if we're looking up font metrics, so
tweak the assert.
MANUAL PUSH: Orange fixup CLOSED TREE
This patch includes a preference setting that triggers the execution of element.checkVisibility
only when a form contains fewer than 200 eligible address and credit card fields.
This measure has been implemented to avoid potential performance impact that could occur due
to the visibility check running on a large number of elements.
Differential Revision: https://phabricator.services.mozilla.com/D178308
https://drafts.csswg.org/mediaqueries-5/#mq-boolean-context is pretty
clear:
> If the feature would be true for any value other than the number 0, a
> <dimension> with the value 0, the keyword none, or a value explicitly
> defined by that media feature to evaluate as false in a boolean
> context, the media feature evaluates to true.
> Otherwise, it evaluates to false.
These hit the "otherwise". The unknown behavior might make sense, but if
someone wants it the spec needs to change (for all media features
consistently).
Differential Revision: https://phabricator.services.mozilla.com/D178712
This patch includes a preference setting that triggers the execution of element.checkVisibility
only when a form contains fewer than 200 eligible address and credit card fields.
This measure has been implemented to avoid potential performance impact that could occur due
to the visibility check running on a large number of elements.
Differential Revision: https://phabricator.services.mozilla.com/D178308
André Bargull
serge-sans-paille
Eemeli Aro
Gijs Kruitbosch
James Teh
Emilio Cobos Álvarez
Otto Länd
Dimi
Andreas Pehrson
Noemi Erli
Ziran Sun
Julian Descottes
Julien Cristau
Hubert Boma Manilla
Mark Banner