Remove image_overrides custom replacing the QR code for FOCUS message and instead use a separate message for de locale that also configures the links correctly like the KLAR message.
Differential Revision: https://phabricator.services.mozilla.com/D157518
On Windows, when an alert is privileged and `name` is non-empty, round
trip its `name` (as `privilegedName`) through the Windows notification
mechanism, and provide it to the "relaunch" callback.
Differential Revision: https://phabricator.services.mozilla.com/D156636
I don't see any reason to keep this under the same namespace as the other former `privacySegmentation` prefs - but perhaps I'm missing something here.
Depends on D156733
Differential Revision: https://phabricator.services.mozilla.com/D156734
Everything here is Windows-only for now, since that's the immediate
use case and these implementation details are specific to Windows
native notifications relaunching Firefox when it is not running --
functionality not supported by the other system alert backends at this
time.
This commit adds a `launch_url` parameter to `ToastNotification`.
This should be viewed as the simplest possible "action" that a toast
notification can take when it is clicked, namely navigating to the
given URL. In the future, we might generalize this to describe more
of the existing actions (like opening settings, snoozing or dismissing
the toast, etc), but for now, this handles my use case.
In addition, this uses `content.tag` as the alert `name`, allowing to
replace existing toast notifications.
Differential Revision: https://phabricator.services.mozilla.com/D155912
Add new properties to ProtonScreen logos: reducedMotionImageURL and
darkModeReducedMotionImageURL. These are intended to be used when
imageURL and/or darkModeImageURL is an animated image such as a GIF. If
reduced motion images are passed, they will be used instead of
imageURL/darkModeImageURL if the user has enabled a reduced motion
preference through their OS or Firefox settings. So, consumers can pass
up to 4 logo URLs to be matched with the following media queries:
1. imageURL: not (prefers-color-scheme: dark)
2. darkModeImageURL: (prefers-color-scheme: dark)
3. reducedMotionImageURL: (prefers-reduced-motion: reduce)
4. darkModeReducedMotionImageURL: (prefers-color-scheme: dark) and (prefers-reduced-motion: reduce)
Differential Revision: https://phabricator.services.mozilla.com/D155037
Add new properties to ProtonScreen logos: reducedMotionImageURL and
darkModeReducedMotionImageURL. These are intended to be used when
imageURL and/or darkModeImageURL is an animated image such as a GIF. If
reduced motion images are passed, they will be used instead of
imageURL/darkModeImageURL if the user has enabled a reduced motion
preference through their OS or Firefox settings. So, consumers can pass
up to 4 logo URLs to be matched with the following media queries:
1. imageURL: not (prefers-color-scheme: dark)
2. darkModeImageURL: (prefers-color-scheme: dark)
3. reducedMotionImageURL: (prefers-reduced-motion: reduce)
4. darkModeReducedMotionImageURL: (prefers-color-scheme: dark) and (prefers-reduced-motion: reduce)
Differential Revision: https://phabricator.services.mozilla.com/D155037
To be used in about:privatebrowsing Pin Private Window promo message. BLOCK_MESSAGE will be used in a multi action call after user clicks 'Pin To taskbar'. This will help in hiding Pin promo message on current and preloaded tabs
Differential Revision: https://phabricator.services.mozilla.com/D151888
The Nimbus Features corresponding to FxMS messaging surfaces are actually
intended to map to FxMS message groups, which can accept *any* FxMS message.
The features have been updated with schemas that accept any FxMS message.
As part of this, all FxMS schemas have been updated with an `$id` so that they
can be bundled into feature schemas and have their internal `$ref`s work.
(Otherwise, a `$ref` would be relative to the top-level schema instead of the
sub-schema).
Schemas for individual message types are no longer exposed as resource:// URIs,
except in tests, as indivual schemas are no longer required at runtime.
Additionally, each FxMS schema has had its `template` field become required and
requires a constant value for that schema (e.g., Spotlight requires a template
value of "spotlight").
A test has been added to ensure that if any of the messaging surfaces schemas
change that the feature schemas are also updated. The feature schemas can be
regenerated via:
```
cd ./browser/components/newtab/content-src/asrouter/schemas
../../../../../../mach make-schemas.py
```
Differential Revision: https://phabricator.services.mozilla.com/D147332
Make the width and font sizes match the spec. Clean up button sizing. Remove lots of
unnecessary font-size overrides. Fix the margin for large size icons. Fix
the test PERSONALIZED_CFR_MESSAGE doorhanger and update it with a large
size icon to make it possible to test and debug.
Differential Revision: https://phabricator.services.mozilla.com/D129281
