Absolutely positioned elements should be given the scroll root of their
containing block and not necessarily the scroll root of their parent.
This fixes several CSS tests, though others are still failing pending a
similar fix for inherited clipping rectangles.
Fixes#13530.
<!-- Please describe your changes on the following line: -->
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: -->
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
- [ ] These changes fix #__ (github issue number if applicable).
<!-- Either: -->
- [x] There are tests for these changes OR
- [ ] These changes do not require tests because _____
<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
Source-Repo: https://github.com/servo/servo
Source-Revision: 9f5b17202fb87bf84230dd7db0a767c330be8c7b
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 77d0c5057f306e10b161a8d05f8f8b50d7ffd886
This patch updates the description for the probes SSL_CIPHER_SUITE_FULL and
SSL_CIPHER_SUITE_RESUMED found in Histograms.json to point to
AccumulateCipherSuite which contains the key exchanges instead of the previous
HandshakeCallback.
MozReview-Commit-ID: Bf3xKGdK4Sd
--HG--
extra : rebase_source : e278f28e6abf4044d0e554dd28bd2d550c576ef2
This shortens the name of the quitApplication Marionette command to
`quit'.
The client is not updated since it is used for Firefox upgrade tests.
It can be updated to use `quit' when Firefox 56 ships.
MozReview-Commit-ID: Gq5KWMS1AzF
--HG--
extra : rebase_source : dfaf557f658595bfa5b8d1d294d6d6525f5d2abf
This adds a return type to the quitApplication command in Marionette,
which extracts the data received by the quit-application observer.
The returned cause is either "shutdown" or "restart".
MozReview-Commit-ID: 85fBGaS1VeQ
--HG--
extra : rebase_source : f96409b772a2c30e755b5a28b6e4eef1dcfb2654
Change Marionette's quitApplication command to accept an optional array
of masks for Services.startup.quit. If no masks are provided or the flags
field is not provided, we assume nsIAppInfo.eAttemptQuit as the default.
This deviates from the current behaviour whereby eAttemptQuit is
unconditionally included when passed an array of flags. This is
problematic because Services.startup.quit does not allow combinations
of *Quit flags, e.g. eAttemptQuit and eForceQuit cannot be combined.
MozReview-Commit-ID: FVqdaXFA4aC
--HG--
extra : rebase_source : 10074c53294a6596ecbd09a3f6ec477f3f8ed452
When Marionette receives packets it does not know how to deal with,
handle this gracefully and attempt to respond to the client that we were
unable to process them.
If it receives a packet that is corrupt, e.g. one it is impossible to
determine the message ID of, report an error to the console without
failing spectacularly.
If it receives a packet that it is unable to unmarshal, attempt to craft
a response for it with containing the error signature.
MozReview-Commit-ID: BLi8yIkGQfF
--HG--
extra : rebase_source : e7dc763a2345f79712b5e8524bd1d4f81b66699c
This change introduces more data validation checks on unmarshaling
Marionette protocol messages. Specifically, validation of
message.Command's and message.Response's constructor arguments and packet
contents in their respective fromMsg functions are tested.
Doing these tests ensures more safety further down the pipeline with
respect to the data integrity in Marionette commands.
MozReview-Commit-ID: BxYipX5zfo9
--HG--
extra : rebase_source : 5cd9edab8801323b19688f871ba78ccf70a05c5e
The fourth element of the command packet may be null and for that to
hit our default type check in message.Command's constructor we need to
interpret null as undefined.
This allows us to receive packets such as
[<number>, <number>, <string>, <null or value>]
MozReview-Commit-ID: EcAmsPAzz5p
--HG--
extra : rebase_source : c3613c85a4b5383d2894d9b102eee16c02935236
This patch adds an accumulation limit to Scalars IPC messages,
in a similar way as this limit was already implemented for Histograms.
After a discussion in the bug entry, 10000 was chosen as limit.
MozReview-Commit-ID: ARBUOFnfDBr
--HG--
extra : rebase_source : 353e35fe1cf37d1ebad1e54ac9d329a958f95dc3
We are going to need this in the future and starting collection even before releasing
Activity Stream will create a better experience once we turn it on.
And this flag is hard to miss. So let's just get rid of it.
MozReview-Commit-ID: 5oDzXhpQdSA
--HG--
extra : rebase_source : c96800257070af9287d5236625150dbb62985c4b
This is a bit complicated. But most of that code should go away again as soon as
we can stop shipping the opt-out preference.
With this patch we have three flags that can be controlled via Switchboard:
* activity-stream: This is our global kill switch and allows us to pull the feature
if needed. A user has to be in this experiment to ever see activity stream. The
goal is to enable this experiment for 100% of the Nightly audience.
* activity-stream-opt-out: This is experiment will enable the Activity Stream by
default. The goal is to enable this experiment for 50% of the Nightly audience.
* activity-stream-settings: This experiment controls the visibility of a setting
to enable/disable activity stream (settings -> advanced -> experimental features).
This allows us to control whether users can opt-in or opt-out of the activity
experiment. The goal is to enable this for 100% of the Nightly audience.
MozReview-Commit-ID: BwEoTK6QMQx
--HG--
extra : rebase_source : dbe9815127c1aa620bbc2f1623aa4726438d3285
The UpdateAnimationsTasks is a bitflags and each bit is generated from
Gecko's UpdateAnimationsTasks (enum class) values for matching values
between C++ and Rust. For this reason, the bitflags is annotated as
(feature = "gecko"), as a result update_animations() which uses this bitflags
also became gecko-only function.
MozReview-Commit-ID: AfQd0FJGkYd
--HG--
extra : rebase_source : 2a5fee40c57a7941defa447357915756af42bc11
We will use this function for stylo computed values as well.
MozReview-Commit-ID: IxDg4EZARi3
--HG--
extra : rebase_source : dc6445ab0c836393913d64313c8151f31cd7b523
If an element has any type of animations in match_elements(), we need to call
UpdateEffectProperties() to update KeyframeEffectReadOnly::mProperties.
MozReview-Commit-ID: 1CDhwoM2llE
--HG--
extra : rebase_source : f2c476d579019079702b01fec375f75b4594dee9
Gecko_ElementHasCSSAnimations is not called against pseudo elements
other than ::before or ::after.
MozReview-Commit-ID: EtHoLhX5P9h
--HG--
extra : rebase_source : 534fe74280bc6cd7362ee7580a83d0a9af8e164f
<!-- Please describe your changes on the following line: -->
This is a PR of https://bugzilla.mozilla.org/show_bug.cgi?id=1350754
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
<!-- Either: -->
- [X] These changes do not require tests because it's for stylo
<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
Source-Repo: https://github.com/servo/servo
Source-Revision: 1e2b36a97a9391e274d924227a8857024dbe4774
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 81f6907eb040b5727ba39aa14ab5cd1edf7871b8
The test does nothing if the animated images discarding pref isn't enabled.
--HG--
rename : image/test/crashtests/1249576-1.png => image/test/mochitest/infinite-apng.png
In Bug 1334241 we turned on 'privacy.trackingprotection.annotate_channels'
preference by default, but this cause regressions like Bug 1334616 and
Bug 1325054. The right fix is landed in central, for aurora we could just
backout the change made in Bug 1334241 for simplicity.
MozReview-Commit-ID: INuFdD04AwJ
--HG--
extra : rebase_source : 93dc469d6e91777bf20bc91531c59ca5efb3fd45
The 5s timeout was not enough for debug builds. I don't really see a
reason to use something other than the default socket timeout here.
MozReview-Commit-ID: Fm5lgSI3lFb
--HG--
extra : rebase_source : d0d598f292702e50350237df35bf44bfc185a958
These should work now that we have GeckoDriver 0.15 in tree.
MozReview-Commit-ID: J9AigCBrOMl
--HG--
extra : rebase_source : e92b6980ac05758eacc36f470bf276d6ee926d25
Add a new attribute "rawValue" in each of the numeric fields. We store the
non-formatted number in this attribute, and display formatted number using
Intl.NumberFormat.
MozReview-Commit-ID: JkcBObFoYQ3
--HG--
extra : rebase_source : 05918ba57513f9c816273a758ab2aa7198722135
nsIX509Cert.getAllTokenNames() is only used (improperly) to determine if a
certificate is a built-in. nsIX509Cert.isBuiltInRoot should be used instead.
MozReview-Commit-ID: LBwI8nTc05C
--HG--
extra : rebase_source : 9494cd1243395b0d293022e981f64be560a54dec