When .rel.plt and .relr.dyn are the same size, after the section header
for .relr.dyn has been updated, it matches the condition for .rel.plt,
and we ended up undoing the change.
Differential Revision: https://phabricator.services.mozilla.com/D192981
In bug 1755863, we introduce two async APIs in `nsIClipboard` to make async
clipboard API reads the clipboard data asynchronously. When reading, async
clipboard API first check the available types, and then retrieve the actual data
for that type. This process has a potential race condition: the clipboard content
might change between the time between the time we check the types and when we
retrieve the data. Although we currently fetch the actual data immediately after
checking available types (in line with the spec), this minimizes the chance of
encountering this race condition. However, if we would like to support retrieving
the data only when `getType()` is invoked (bug 1691825), this potential race
condition could become a significant issue.
Furthermore, bug 1777448 aims to have a way to track the clipboard data and suppress
the paste context menu when the clipboard data originates from a same-origin page.
This also requires a better way to track read requests, clipboard content and
invalidate the request when the system's clipboard content is changed.
After some refacting around nsBaseClipboard, all platform now use sequence
number to track clipboard content, so `nsIAsyncGetClipboardData` can be associated
with a sequence number and deemed invalid if the associated sequence number isn't
matched the latest system value.
With these new API, it also becomes possible to write some tests.
Depends on D191409
Differential Revision: https://phabricator.services.mozilla.com/D182108
The PDF Viewer notification bar became unused in bug 1705327, which is well over two years ago, hence it seems reasonable to stop shipping this code when it's not being used.
Differential Revision: https://phabricator.services.mozilla.com/D193056
This is needed to be able to use chrome environment variables in
chrome stylesheets and have them work in non-chrome documents.
This will be used to communicate the right transition duration in
scrollbars.css, but should also be useful to have the right base URI for
<url>-typed custom properties.
Differential Revision: https://phabricator.services.mozilla.com/D193048
SharedArrayBuffer can only easily be testing through dom.postMessage.sharedArrayBuffer.bypassCOOP_COEP.insecure.enabled
preference which is locked on beta and release channels.
Differential Revision: https://phabricator.services.mozilla.com/D192942
`mFileDialogInstance` is not needed, since we don't reuse old file-
dialog actors. (We _do_ reuse active file-dialog utility processes as
hosts for those actors; this check is a leftover from when that was
expected not to be the case.)
Differential Revision: https://phabricator.services.mozilla.com/D192983
This change adds a new code block section to help developers visualize
their changes before creating commits. Additionally, adds an example
of a good commit message to help new contributors with our commit
message format.
We also clarify some links by adding more context to the text.
Additionally, we clarify some of the sections in the stack_quickref
document.
Differential Revision: https://phabricator.services.mozilla.com/D192978
The test ensures LCP doesn't expose the state of soft-navigation. Since
this is something that we don't support, I think it's okay to not bother
with it.
Differential Revision: https://phabricator.services.mozilla.com/D192963
This adds support for the experimental `invoketarget` and `invokeaction`
attributes, as specified in the open-ui "Invokers" explainer.
(https://open-ui.org/components/invokers.explainer/)
The `invoketarget` attribute maps to the IDL `invokeTargetElement`,
similar to `popoverTargetElement`, and the `invokeaction` is a freeform
string.
The Button behaviour checks for `invokeTargetElement` in its activation
behaviour, and dispatches an `InvokeEvent` if there is one.
This also adds some basic scaffolding for `handleInvokeInternal` which
will allow elements to provide their own invocation action algorithms.
Differential Revision: https://phabricator.services.mozilla.com/D190449
There might be multiple LCP entries in a web page, and we only care about the
last one which is also the biggest value. That's why we need to record these
values in two different places:
- During the Document unload, so we can add markers for the closed pages.
- During the profile capture, so we can add markers for the open pages.
This allows us to capture all the LCP values. Note that this is not the case
for other metrics like FCP, TTFB, DOMContentLoaded etc. that fires only once.
Differential Revision: https://phabricator.services.mozilla.com/D192828
- Update WAKE_LOCK_LOG to print 'this' which allows to sort operations by lock type
- GetOrInsertNew() call always creates a new WakeLockTopic object so in this patch call it only if we create a new object.
- Split mWaitingForDBusReply to mWaitingForDBusInhibit/mWaitingForDBusUninhibit. It allows to ignore repeated requests and also cancel
opposite requests.
- Use g_cancellable to cancel pending DBus operation if we want different wake lock action.
Differential Revision: https://phabricator.services.mozilla.com/D192622
GetAndInitDeviceDisplay() uses DrmRenderDevice to create GL context over drm device so we should set it even if dmabuf operations are disabled.
Differential Revision: https://phabricator.services.mozilla.com/D192933
- Update WAKE_LOCK_LOG to print 'this' which allows to sort operations by lock type
- GetOrInsertNew() call always creates a new WakeLockTopic object so in this patch call it only if we create a new object.
- Split mWaitingForDBusReply to mWaitingForDBusInhibit/mWaitingForDBusUninhibit. It allows to ignore repeated requests and also cancel
opposite requests.
- Use g_cancellable to cancel pending DBus operation if we want different wake lock action.
Differential Revision: https://phabricator.services.mozilla.com/D192622