The old system required wasm::DisableHugeMemory() to be called
before anyone calls wasm::HugeMemoryEnabled(), and enforced that with
some runtime checks.
We had a bug where GetOptimizedBuildEncodingId() (which queries the
huge memory flag) would be called by Gecko before we read the pref.
This commit refactors this code to use a JS::Pref instead which is
always set before JS_Init() is invoked. This ensures that it is
never changed after we've observed the value and can drop all the
fancy runtime checking.
Differential Revision: https://phabricator.services.mozilla.com/D227273
WRusr.dll injection from WebRoot causes a crash in the utility LPAC
process used for PlayReady because on some versions of Windows,
CallNamedPipeW does COM if it fails to open the pipe in an AppContainer
process. This does not affect other processes though, so blocking
injection in utility processes should be enough.
Differential Revision: https://phabricator.services.mozilla.com/D228185
We are wrapping incumbent global into host defined data, and the
this optimization still applies. This patch just renames it.
Differential Revision: https://phabricator.services.mozilla.com/D227841
Automatic update from web-platform-tests
Implement basic structure for dialog light dismiss [1/N]
This CL puts the feature flag in place, adds (flag guarded) closedBy
and requestClose() methods to <dialog>, connects the pointer
events handling to a new dialog light dismiss method, and adds a
basic set of tests. None of the actual functionality is here yet,
this is just a shell. Subsequent CLs will flesh out the behavior.
See spec PR for details:
https://github.com/whatwg/html/pull/10737
Here's the chromestatus:
https://chromestatus.com/feature/5097714453577728
Bug: 376516550
Change-Id: I3727ca21476a2a3340fd18597970395d64ef7176
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5985491
Commit-Queue: Mason Freed <masonf@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1378633}
--
wpt-commits: 1d5037cc3ff4524fd5d9f1a461afd20aebbb0839
wpt-pr: 48976
Automatic update from web-platform-tests
Don't update LCP for video elements switching from poster.
A video element whose rendered contents are a poster image will have a
different MediaTiming than when it's contents are the video itself.
However, that different object will cause the MediaRecordId to be
different, and so the same element can create two distinct LCP candidate
records.
This change forces the MediaRecordId to not consider the MediaTiming
object when calculating the hash for a video element.
Bug: 330202431
Change-Id: I56b8c8d54c1a3d64138f8de529fe15695b1df952
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5970217
Reviewed-by: Hao Liu <haoliuk@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1378586}
--
wpt-commits: 5fe6c1e7f9ee16db7756262fd2a71232bc9b4d1d
wpt-pr: 48982
Automatic update from web-platform-tests
[CodeHealth] Rewrite PointerEvent modifier WPT using promise_test.
The test was written as an old-style sync tests, used Promise.all
which made any failures hard to debug because of lack of a clear
resolution order, and didn't assert modifier states individually.
This test passes on headless Chrome but not in content_shell!
Bug: 368980630
Change-Id: I69a08aba7b4cd3719c25ca2e9ec76d77bdaea7fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5994451
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Auto-Submit: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1378577}
--
wpt-commits: 0a5ba65a140dc74ade845482466ed03699d0315e
wpt-pr: 48985
Automatic update from web-platform-tests
WebKit export: shape(): support the edge keywords for hline and vline.
https://bugs.webkit.org/show_bug.cgi?id=282015
--
wpt-commits: 813d3cf413970a133d674bbda2b1f1210c47e9e2
wpt-pr: 48984
Automatic update from web-platform-tests
Import new CSS Anchor Positioning tests from WebKit
Added the following tests:
* anchor-in-css-min-max-function-ref.html: tests that anchor() can be used in
CSS min()/max() functions.
* anchor-name-005.html: tests that an anchor with two different anchor names
can be referenced using both names.
--
wpt-commits: 05874e856043806a88f83837b82dc1a34b2b0f70
wpt-pr: 48978
Automatic update from web-platform-tests
Revert "[wptrunner] Clear cookies between testharness tests for Chrome" (#48975)
This workaround allows tests to pass without performing their own cookie
cleanup. Per meeting discussion, revert #48106 until there's a portable
solution.
--
wpt-commits: a8f6d07a02556859fa35ee8b60f3edf1fd75ba38
wpt-pr: 48975
Automatic update from web-platform-tests
Fix assertBothRejectDOM usage (#48972)
Recent changes have replaced promise_rejects_dom with assertBothRejectDOM
but mistakenly have removed the await part, this change fixes that.
Also revert the assertBothRejectDOM change to after-transition-reject.html, the problem
seems to be with the unhandled promise in the handler, not the committed promise.
--
wpt-commits: 96530c133cb8b42c1362fdb4edc75d58b2ce2397
wpt-pr: 48972
Automatic update from web-platform-tests
Use assertBothRejectDOM instead of promise_rejects_dom (#48969)
Not catching promise rejection can (flakily) cause log statements in test results for WebKit.
--
wpt-commits: 0a60381f3b2aa8777cee9302f804c5a19c034cfa
wpt-pr: 48969
Automatic update from web-platform-tests
Add WebDX use counters for cap, ic, and lh units
Also add normal use counters as they didn't exist.
Change-Id: I116e7588d01ddf4005a2dd668e7acaec16d66a3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5987870
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Noam Rosenthal <nrosenthal@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1378186}
--
wpt-commits: 154c2134cdbf099571777a84ac288e9714f3fcd5
wpt-pr: 48957
Automatic update from web-platform-tests
Use assertBothRejectDOM instead of promise_rejects_dom (#48959)
Not catching promise rejection can (flakily) cause log statements in test results for WebKit.
--
wpt-commits: 70dcf32af919da450501cf7d0edae58fcc83a83c
wpt-pr: 48959