This fixes the edit bookmarks dialog by properly allowing stuff to wrap once
the dialog width has been fixed.
Let's try to do this and opt-out any specific pages that may hit issues,
rather than opting-in one by one, now that's early in the cycle?
Differential Revision: https://phabricator.services.mozilla.com/D159690
The sitePermissions code is reused, and all dialogs work OK except the autoplay one.
This is because the autoplay code adds extra content not present in the other
dialogs, and localizes it.
The SubDialog code relies on determining the size of the dialog once the
mozSubDialogReady promise resolves, which it does before fluent puts in l10n data
for the content that was just added. This patch fixes that.
It also, as a driveby, correctly pauses and resumes observing l10n attributes
in the doc when making modifications, to avoid fluent doing a second pass for
the same content.
Differential Revision: https://phabricator.services.mozilla.com/D159543
It seems that at build time, we already make decisions about what migrators we register
with XPCOM in browser/components/migration/components.conf. This doesn't, however, give
us the ability to turn off a migrator that happens to be misbehaving, nor make it easy
for us to do development of a new migrator without exposing it to the migration dialog
(without doing binary recompiles).
This adds another layer to the enable-ment of our migrators so that they must both
be registered AND enabled in order to appear in the import dialog.
Differential Revision: https://phabricator.services.mozilla.com/D159544
On Wayland drop target position can be a negative value. Drop target area can contain empty elements located at 0,0 with zero size.
If we hit such combination the drop element is placed at 0,0 and we don't consider other valid elements located at negative positions.
That leads to incorrect drop target indicatop placement; it's located at 0,0 coordinates.
In this patch we ignore empty elements and iterate through valid ones only so we correctly place drop indicator even when screen coordinates are negative.
Differential Revision: https://phabricator.services.mozilla.com/D159698
This turned out to be more complicated than expected, because:
- SameSite=None requires https://
- Many test were using the mochi.test domain, which is not reachable via https
Differential Revision: https://phabricator.services.mozilla.com/D157637
These workarounds were due to an issue where the sidebar documents weren't having
the LightweightThemeChild instantiated for them on the `pageshow` event. This was
fixed by bug 1596852 about a year ago, so we can remove these workarounds now.
Differential Revision: https://phabricator.services.mozilla.com/D159622
This adds a Nimbus variable corresponding to `browser.urlbar.merino.providers`.
I noticed that when we added a Nimbus variable for client variants (bug
1743685), we didn't actually use it in the provider. Instead we use its fallback
pref. I fixed that too.
Differential Revision: https://phabricator.services.mozilla.com/D159557
Add a new module and feature callout functions to support messages
performing actions when a specified event is dispatched from the
content. This will allow Feature Callout messages to be dismissed when a
button is clicked within the page in which they are rendered. A screen
just needs to provide a `page_event_listeners` property, which is an
array of objects, each containing event listener parameters (event type,
target selector, and optional parameters) and an action specification
like those already used for buttons. The event listener will be added to
all elements matching the selector, so multiple different buttons could
dismiss or advance the message, if necessary. The new screen property
has this form:
```
page_event_listeners: [
{
params: {
type: string,
selectors: string,
options?: {
capture?: boolean,
once?: boolean,
preventDefault?: boolean,
},
},
action: {
type?: string,
data?: object,
dismiss?: boolean,
etc...
},
},
]
```
Differential Revision: https://phabricator.services.mozilla.com/D158899
Rather than having the enterprise policy push engine information to the search service, this pulls it from the policies whilst initialisation is in progress. This will ensure the search service always has the correct information for policy engines even if the search settings file is modified.
Differential Revision: https://phabricator.services.mozilla.com/D156538
For that, we need to min-width: 0 the nav-bar target, which itself
requires us to tweak the overflow detection so that we look at all
children of the customization target, not only the target itself.
Differential Revision: https://phabricator.services.mozilla.com/D159377
Rather than having the enterprise policy push engine information to the search service, this pulls it from the policies whilst initialisation is in progress. This will ensure the search service always has the correct information for policy engines even if the search settings file is modified.
Differential Revision: https://phabricator.services.mozilla.com/D156538
