Automatic update from web-platform-tests
Add checks for popovers moving between documents
Without these checks, we can get into very bad state that can crash the
renderer. This was raised here:
https://github.com/whatwg/html/issues/9177
Change-Id: I3cda0143c76f62709af8593182b4c3a4f8849fd7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4443007
Reviewed-by: Mason Freed <masonf@chromium.org>
Code-Coverage: Findit <findit-for-me@appspot.gserviceaccount.com>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1132191}
--
wpt-commits: 0a40de7a4db9e52cdb0fc436173640756740c9e3
wpt-pr: 39599
Practically speaking, this doesn't make a huge difference, because
libmozglue contains operator new/operator delete overrides. This will
enable inlining opportunities, though.
It is worth noting that there's equivalent code in
js/src/old-configure.in but it's left as is because it is actually no-op
at the moment. This will be fixed in bug 1829049.
The check for __EXCEPTIONS is replaced with __cpp_exceptions because the
former is defined for any type of exception, including ObjC exceptions,
while the latter is defined for C++ exceptions only.
Differential Revision: https://phabricator.services.mozilla.com/D175976
This patch introduces multiple thresholds, depending on platform and color, as
the colors rendered to screen are captured in the display rgb color profile on
Mac and therefore can be significantly off. See bug 1827606 for always capturing
in sRGB.
Differential Revision: https://phabricator.services.mozilla.com/D174754
White is less susceptible to false positives than grey with a high threshold,
given that all its components are at an extreme (255 vs 128).
Differential Revision: https://phabricator.services.mozilla.com/D174753
This adds a card to the about:welcome defaults that embeds the new Migration Wizard
if browser.migrate.content-modal.about-welcome-behavior is set to "embedded".
This requires adding a useEmbeddedMigrationWizard targeting attribute to
ASRouterTargeting.
Differential Revision: https://phabricator.services.mozilla.com/D175945
This is so that the contents of the Migration Wizard don't get automatically
centered if its embedding context is centering things.
This change also makes it so that embedders can customize some of the rules of how
buttons are laid out.
Differential Revision: https://phabricator.services.mozilla.com/D171771
@jimb expressed concern that a collapsed group of compilation messages for WebGPU shaders in the JS console isn't easy enough to discern from scanning a console log manually. We can't associate a log level with the group itself (which would let us paint the group with color for contrast), unfortunately. So, we decided to have a "sentinel" message right before groups that uses the highest "severity" of message in the entire set of compilation messages.
Differential Revision: https://phabricator.services.mozilla.com/D175404
Time to finally add some (barebones) diagnostics! When a user calls [`GPUDevice.createShaderModule`], if there are any messages returned:
1. Create a collapsed console group. Use a generic title for the console group (for now).
1. Inside the console group, print containing a log entry per message with a JS log level according to the message severity.
Differential Revision: https://phabricator.services.mozilla.com/D175303
After landing bug 1673068, `LoadURIDelegate.jsm` isn't used until error page
is shown. This should move to lazy and convert to ES system module.
Differential Revision: https://phabricator.services.mozilla.com/D175661
Due to design constraints, it is difficult for osclientcerts to properly
indicate whether or not each known key supports RSA-PSS. Ideally such a
determination would be made close to when a particular key is going to be used,
but due to the design of PKCS#11 and NSS' tight coupling to it, osclientcerts
would have to make this determination when searching for all known keys, which
has been shown to be prohibitively slow on Windows and results in unexpected
dialogs on macOS.
Thus, previously osclientcerts simply assumed all RSA keys supported RSA-PSS.
This has resulted in handshake failures when a server indicates that it accepts
RSA-PSS signatures.
This patch instead makes RSA-PSS support configurable via a pref
(security.osclientcerts.assume_rsa_pss_support). If the pref is true,
osclientcerts assumes all RSA keys support RSA-PSS. If it is false, it assumes
no RSA keys support RSA-PSS.
Differential Revision: https://phabricator.services.mozilla.com/D175966
ShouldAssert is always yes since I removed the native anonymous child
list thing, so we can just assert always.
The remaining customization is only about whether we should notify
the pres shell before or after the rest of the observer (we only need to
notify before for removals).
We only need one notifier thingie, since pres shell is an
nsIMutationObserver.
Differential Revision: https://phabricator.services.mozilla.com/D176077
We use many variations of 'global data', 'global area', and more recently
'instance data'. I prefer 'instance data' as 'global' is ambiguous with
wasm globals, which while stored in the instance are not the only thing
stored there. The naming scheme for this originated when globals were
the only thing stored there, so we should now change it.
Depends on D172026
Differential Revision: https://phabricator.services.mozilla.com/D172027
BaseCompiler::loadTypeDef assumes that it can use InstanceReg, but that
is only true on non x86/arm32.
This commit removes loadWasmGlobalPtr, as it's just a thin wrapper around
loadPtr that obscures more than helps. Callers of that now just specify
the register that contains the instance directly. This demystifies what's
going on. We can then fix baseline to use a register it has allocated.
Differential Revision: https://phabricator.services.mozilla.com/D172026
