beforeTestSync uses an asynchronous operation that takes a while to finish.
In the meantime, it's very likely that the browser will run some tasks
scheduled to run when idle, which cause XPCOMUtils mock in browser-test.js
to be used, which references _globalProperties.
--HG--
extra : rebase_source : 3d75068a43cad4e87317792c67b6fe5fd483f0c5
TypedObjects that map Wasm structs with fields that have Ref type are
not yet constructible from JS because the type constraint can't be
honored. So for now, make it possible for Wasm to flag such structs
as unconstructible-from-JS.
--HG--
extra : rebase_source : aab9d7f2ba7b4c1ff7875d184b86bb0ae3e32413
extra : intermediate-source : 97c72ae6e843fe1cb712bd4855d174fc711c3cb0
extra : source : f59588ebc5c4ff06bfb437896147e07cb856e355
This allows internal clients (notably Wasm) to flag TO fields as
immutable; we need this both to provide immutability for fields that
are declared immutable in wasm structs, and to temporarily avoid the
need for type constraints on assignments to Ref-typed pointer fields.
--HG--
extra : rebase_source : 19d1b1bf81396ca305b699cda0277fd8e41f5fe9
extra : intermediate-source : d219c9587f920a0f5924dbdab3e8cf5dfecf3f75
extra : source : f1161dd31ac1cf6f050315d04b978b9d6c0c824a
Struct types need to appear to be callable, or some paths through the
engine will not think that they are constructors (since constructors
are callable).
They are not *actually* callable however; the call implementation
always throws.
--HG--
extra : rebase_source : a0db93050943bda3348887c8a63a374e19158d41
extra : source : 437198f32338d69602f3375f94a996f3d880fa17
In the old days we could only share a SharedArrayBuffer, but now we
can also share WasmMemory and WasmModule objects. Rename the shell's
get/setSharedArrayBuffer as get/setSharedObject and generalize them to
handle the new types.
Leave the old names in place as aliases of the new names.
We rename /some/ uses of get/setSharedArrayBuffer in existing test
cases, but leave uses in test262 alone; we need to upstream those more
carefully.
--HG--
extra : rebase_source : 5ca04306a739249a70fc4aa8734b08e16d62f7d4
extra : source : fcd471c23cf3c1374541df766fd5aea0628fb2a5
Automatic update from web-platform-testsHTML event handlers: More uniform naming convention
--
HTML event handlers: Use .window.js instead of .html for some files
--
HTML event handlers: Use IDL parser for list of event handlers
--
HTML event handlers: Use synchronous test() where able
--
HTML event handlers: Additionally test unshadowed event handlers
--
HTML: tests for new event handler spec
See: https://github.com/whatwg/html/pull/3850
--
HTML event handlers: Test document.createElement("body")
--
wpt-commits: db24506f8af9048c0a80d89c9981ef445d6c3af9, 3e273bc58ae2af40f4b00b514f2fd6d604ffc98d, 8bf45a39c3435737ebc862904af245d27b68efce, 776041862ca0cab7a8dd10e29361dbf3359a0b2f, fa58a12fc565fc152bff196e803fd9290dfa1bc7, fc2eba9d6f0a860c0db1457852124e320fd8d499, 8e668a6b63e5dbb68304c182fdc1f7b4e6edaf96
wpt-pr: 12201
Automatic update from web-platform-testsAdd UserActivation member to MessageEvent
Add an API to query user activation state on a posted message event.
Add includeUserActivation attribute on the WindowPostMessageOptions so
that indication of user gesture behavior can be opted in.
https://github.com/dtapuska/useractivationhttps://github.com/whatwg/html/issues/1983
BUG=846858
TBR=mkwst@chromium.org
Change-Id: I2459b21004afbe00c41ddf992533c60728768bb4
Reviewed-on: https://chromium-review.googlesource.com/1131558
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579398}
--
wpt-commits: 8a1d5c110779c525257fe2305ba7a21ae6e969e6
wpt-pr: 12157
Automatic update from web-platform-testsAvoid using the JavaScript reserved word `arguments`
ES6 complains if the JS reserved word `arguments` is used in strict
mode. Rename variable to avoid issues --- especially when test cases
are reused with other test harnesses.
--
wpt-commits: fe830a9732f4748d37a932d1b2c813e2ed47d491
wpt-pr: 12213
Automatic update from web-platform-testsClean up the BackgroundSync IDL test (#12242)
--
wpt-commits: f1d7391442edcdb97bbf968b2ff631c387e3a8ef
wpt-pr: 12242
Automatic update from web-platform-testsMark some tests as failing in python 3.0-3.5. (#11753)
The json.loads API did not accept binary strings in these python versions.
This change does not affect the testing in CI, but helps with certain older
local setups.
--
wpt-commits: 03a5a5cb81912613e15f268a20cfdf919635fe4d
wpt-pr: 11753
Automatic update from web-platform-testsCreate a dictionary of {item_type: ManifestItemClass}
Sometimes we need to know all the types of test that exist. Typically
this has either been done by hardcoding a list or using some custom
approach to finding all the subclasses of the original. Instead it
makes sense to have the classes register themselves on creation so
that we can simply look in the registry for the types.
To do this we use a cusom metaclass that first constucts the class
object and then adds it to the registry.
--
wpt-commits: 76d1afcb887b5911e0151ff0be991a267d70d0a1
wpt-pr: 12229
Automatic update from web-platform-testsMigrate Background Fetch layout tests to WPT
This CL migrates our Background Fetch layout tests to our WPT suite, and
adds coverage in various new areas, together with a few minor bug fixes.
Tests related to initializing the Service Worker events haven't been
included as the event model has just been updated. New tests will be
added based on that soon.
One file which was removed without being migrated was
"credentials-in-url.https.window.js". This was testing the Fetch API as
opposed to Background Fetch. Instead, the requirement to propagate
exceptions thrown by the Fetch API is tested in fetch.https.window.js.
Bug: 864561
Change-Id: I077be6c5bf8c379e3108f4ec3207011582028477
Reviewed-on: https://chromium-review.googlesource.com/1155118
Commit-Queue: Peter Beverloo <peter@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579370}
--
wpt-commits: fb974dd68affa515d39feee51f8fb4ba818ca13b
wpt-pr: 12234
Automatic update from web-platform-testsFix RTCPeerConnection-transceivers.https.html bug.
This PR accidentally made the "addTrack(0 streams)" test call addTrack()
with a stream, which broke the tests:
https://github.com/web-platform-tests/wpt/pull/12141
Test restored and all "addTrack/addTransceiver(X streams)" are made to
consistently use "new MediaStream()" the same way.
Bug: 869036
Change-Id: Ieaf0c73a1996aeb2e87e18f2f9065fa1e6fee1e7
Reviewed-on: https://chromium-review.googlesource.com/1155125
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579341}
--
wpt-commits: 6468c69f9f9e5925f6af370ad127a72c3adc14ed
wpt-pr: 12237
Automatic update from web-platform-testsMove the transfer object into WindowPostMessageOptions
Spec changes were requested and this change matches the spec changes.
https://github.com/whatwg/html/issues/3799
BUG=861735
Change-Id: Ie5f33e6d52eb5d904ae3c439ee488ab75a3b514d
Reviewed-on: https://chromium-review.googlesource.com/1151388
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579152}
--
wpt-commits: defe19d91c59decb804193cbc0137e6a8465367a
wpt-pr: 12212
Automatic update from web-platform-tests[LayoutNG] Add support for negative margins and new formatting contexts
This does two things:
1. Allows a new formatting context to be sized and positioned outside
its layout opportunity when negative margins are present.
This occurs when a layout opportunity inline dimensions matches the
initial child available space (ignoring floats).
Additionally when a new formatting context "jumps out" of its layout
opportunity it ignores any floats which might impede it.
2. Performs layout inside an opportunity, and then checks if the result
can fit within the same opportunity. Previously we were trying to
position in an arbitrary layout opportunity, which fails the
new-fc-relayout.html test.
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I6b44b6273be5c0f633e39a8875cc54ea0bc54480
Bug: 635619
Reviewed-on: https://chromium-review.googlesource.com/1150849
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579064}
--
wpt-commits: fe2c977518e90340f1a88606fa8844577d577028
wpt-pr: 12204
It's write-only.
Looks like this became unused in bug 501847 when we changed how ib splits work
and no longer needed this information.
Differential Revision: https://phabricator.services.mozilla.com/D2521
MozReview-Commit-ID: GDwcheP3bV4
It was needed presumably because XBL could override the tag name and what not.
But I removed that capability for elements other than XUL elements, so we can
just poke at the content directly.
Differential Revision: https://phabricator.services.mozilla.com/D2520
MozReview-Commit-ID: B5Ihu0gaNd8
