This includes, for example :hover.
Also removes the call to IsStyledByServo() in the document constructor, it's not
only unnecessary, but also we call UpdateStyleBackendType() too early.
MozReview-Commit-ID: 4YfCdmLoSxu
This is to avoid changing the access modifiers.
MozReview-Commit-ID: 9kkWeAKelGL
--HG--
extra : rebase_source : 67a3995872fff4a5028ce86ea070078635ba17e9
When the autocomplete popup has a scrollbar, the rightmost part
of the suggestions is hidden when using RTL locale.
XUL autocompletes (using the richlistbox) were always displaying the
suggestions using LTR. I couldn't find any CSS rule enforcing this, so
I assume this was a default behavior of the richlist box.
This patch restores the same behavior as before.
MozReview-Commit-ID: 9AcMxEe6tuL
--HG--
extra : rebase_source : 9329892b3d387739ffc9c53d3c89b3a30e8833ff
Two bools are not converted because they are used with AutoRestore.
MozReview-Commit-ID: AjU61eiMtlQ
--HG--
extra : rebase_source : d1706adc6f14a1a93d1461dd22df0a95043fcca4
CLOSED TREE
--HG--
extra : amend_source : bfa17aa47bbb5d5e7f51f467fcae24d082b2989f
extra : histedit_source : 4db9a64c9d9704f9aecb65e213e05566d91a5847%2C5b92529a8a7fdff1f8d319c8208f0cb525a716eb
This adds reftest support to the test package mach environment. It will allow
developers to easily run reftests after checking out an interactive worker.
MozReview-Commit-ID: fBAbfuG5XQ
--HG--
extra : rebase_source : 84b4a9fff7f2f27a325ffad4af1de7726bad296e
This adds the 'xpcshell-test' command to the mach environment found in the test
package. This will allow developers to easily run xpcshell after checking out
and interactive worker.
MozReview-Commit-ID: fBAbfuG5XQ
--HG--
extra : rebase_source : 71077c9142f33843ed87d4bc4617a780f775939b
The test path structure is slightly different in the test package compared to a srcdir. So we may need
to normalize the specified paths such that they are relative to a srcdir. Because every test harness
needs to do this, this method is being added to the bootstrap for re-use.
MozReview-Commit-ID: fBAbfuG5XQ
--HG--
extra : rebase_source : b4cedaecfeab777971c9840e932c0aa2bff88240
When running test harnesses from the test package, the firefox binary will live somewhere
outside of the mach context. There are two common situations where a developer might be
running from a test package:
1) From a mozharness context
2) From an objdir context
This patch will attempt to detect either of those situations and automagically find the
firefox binary.
MozReview-Commit-ID: fBAbfuG5XQ
--HG--
extra : rebase_source : 53c87a83bacf6b90a5849559f5616b7a45970627
The spec now defines that we should use the relevant Realm of the target
element for the created Animation and KeyframeEffect object.[1] As for the
AnimationEffectTiming object associated with the KeyframeEffect object,
the constructor for KeyframeEffect (or, actually the constructor for
KeyframeEffectReadOnly), specifies that current realm is used (which, at this
point corresponds to the relevant Realm of the target).[2]
[1] https://w3c.github.io/web-animations/#dom-animatable-animate
[2] https://w3c.github.io/web-animations/#dom-keyframeeffectreadonly-keyframeeffectreadonly
MozReview-Commit-ID: HzlyCxeQZ3T
--HG--
extra : rebase_source : c27363907da4a6e9ef1327c2ab1f06e8f6129585
Previously, when fetching an nsPresShell, we would look up the current realm
document and get the pres shell for it. This patch makes us call GetPresShell()
which uses GetRenderedDocument() which corresponds to the composed document of
the target effect which seems more consistent since it is the target effect we
will use as context for computing CSS values (as required by [1]).
[1] https://w3c.github.io/web-animations/#calculating-computed-keyframes
MozReview-Commit-ID: 9S55041rfTp
--HG--
extra : rebase_source : c52d4c366d0a2891958c8f7378614a8feb5e7c70
