This would help in the case where it is safe to run script in-place and
the CustomElementDefinition is available before the function exits.
This fixes the tests changed.
MozReview-Commit-ID: Ays91W94WZm
--HG--
extra : rebase_source : 6b0f1f90de9a6bfd7db577f1fb0e76564c3627e7
extra : source : 47c62a1e2f268e1be24c3fddfc006c3ad45ba4ac
This defines three flushing functions that flush different parts of the
WR pipeline. Using all three guarantees that everything sent to WR will
have been flushed. This is what we need to do in SyncWithCompositor to
ensure that it meets the API contract.
In addition, this patch updates the existing FlushRendering function to
use the new functions (no functional changes intended here).
MozReview-Commit-ID: GzxwpF4JT04
--HG--
extra : rebase_source : 1a8cf434d1280902906da257ae63751da7ffd114
Instead of notifying the AsyncImagePipelineManager on the compositor
thread via the CompositorBridgeParent, we can send it the new pipeline
info directly from the RenderThread after the update happens. This
effectively splits the AsyncImagePipelineManager update-processing into
two parts: one that takes in the new pipeline info and one that process
it. This allows us to invoke the processing step from other code running
on the compositor thread, which we will need to do in the next patch.
MozReview-Commit-ID: 7xhm8I7bY4C
--HG--
extra : rebase_source : bfa62e326fd830bc2ef771138e5008fb2bc0d6b8
We do a silent upcast from CompositorBridgeParent* to the base class and
pass it around as a CompositorBridgeParentBase* for no reason. Avoiding
this simplifies the code slightly and avoids virtual function overhead.
We do need to move a couple of functions in CompositorBridgeParent from
protected scope to public scope.
MozReview-Commit-ID: 9Zq3GwxEXpr
--HG--
extra : rebase_source : 67346159e7d99ca7fc2fe0052e85aa6618b50d27
WebAssembly.Global is currently nightly- and early-beta-only, gated by
ENABLE_WASM_GLOBAL and EARLY_BETA_OR_EARLIER respectively. This bug is to
enable it by default.
* js/src/moz.build:
js/src/shell/moz.build:
js/src/jsapi-tests/moz.build:
Don't define ENABLE_WASM_GLOBAL.
* js/src/wasm/WasmJS.cpp:
js/src/wasm/WasmModule.cpp:
js/src/wasm/WasmValidate.cpp:
Un-guard code guarded by
#if defined(ENABLE_WASM_GLOBAL) && defined(EARLY_BETA_OR_EARLIER)
and remove code guarded by its negation. Inside js/src, the two symbols
are only ever used together, so there's no need to consider them separately.
* js/src/jit-test/tests/wasm/globals.js:
js/src/jit-test/tests/wasm/spec/harness/index.js:
Remove code guarded by (typeof WebAssembly.Global === "undefined") and
un-guard code guarded by (typeof WebAssembly.Global === "function")
* js/src/jit-test/tests/wasm/spec/globals.wast.js:
js/src/jit-test/tests/wasm/spec/linking.wast.js:
Make these be the same as spec/proposal_mutable_global/globals.wast.js
and spec/proposal_mutable_global/linking.wast.js respectively.
* js/src/jit-test/tests/wasm/spec/proposal_mutable_global/globals.wast.js:
js/src/jit-test/tests/wasm/spec/proposal_mutable_global/linking.wast.js:
js/src/jit-test/tests/wasm/spec/proposal_mutable_global/directives.txt:
js/src/jit-test/tests/wasm/spec/proposal_mutable_global (directory):
Deleted.
--HG--
extra : rebase_source : 72e56b59a5162a2e131596c41ec33f527845ae6d
Pretty much the same setup we have for document.
We have the awkwardness of having to check containing shadow manually for
ShadowRoot because it's not available in TNode (and making it available added a
bit more complexity that wasn't worth it IMO).
MozReview-Commit-ID: CqOh0sLHf6o
The skew resetting of temp I think fixes a bug in presence of skew in every
direction, but again haven't double-checked.
MozReview-Commit-ID: Bn93CoaG8Bu
Per bug 1322189 we really should. I've copied the setup we have already for
translate / scale, but we should really clean this up a bit more I'd think.
In any case, probably skew should be matched as well...
MozReview-Commit-ID: Jky5k8HVfuH
Consider the test-case where we have:
<div>
<span id=a />
<span id=b />
</div>
We try to set one bit on "a", and a different one on "b".
Ideally we'll end up with <div> as the root with both bits. But with the current
code we'd go all the way to the document unnecessarily. This fixes it by
checking the bits we've propagated up to the top instead of existingBits.
MozReview-Commit-ID: GfwjwCBpkuy
This patch:
* Makes StyleStructID an enum class, and moves it to the mozilla namespaces.
* Introduces StyleStructConstants with some constants scattered through the
codebase.
* Makes the computed style bits an enum class, and splits mPseudoType and mBits
into their own members, since we were using a uint64_t when we have only a
couple flags and CSSPseudoElementType is a byte. We statically assert that
the number of style structs is less or equal to 32.
* Makes mPseudoTag, mPseudoType and mBits const, since we don't want them to be
mutated from C++, and we still need a few more refactorings (mostly getting
rid of FinishStyle) to avoid mutating ComputedStyle instead.
MozReview-Commit-ID: 7qsTtASGcYB
Pretty much the same setup we have for document.
We have the awkwardness of having to check containing shadow manually for
ShadowRoot because it's not available in TNode (and making it available added a
bit more complexity that wasn't worth it IMO).
MozReview-Commit-ID: CqOh0sLHf6o
Timothy Guan-tin Chien
Gerald Squelart
Kartikaya Gupta
Markus Stange
Mark Striemer
Ciure Andrei
Geoff Brown
Dorel Luca
Kris Maglione
Julian Seward
Jorg K
Dragan Mladjenovic
Eliza Balazs
Simon Sapin
Emilio Cobos Álvarez
Franziskus Kiefer
Joel Maher
arthur.iakab
Nicolas Silva
Jonathan Kew
James Graham
Matt Woodrow