MozReview-Commit-ID: DYPstPArJWR

Bug 1394323 - Remove overflow css rule for 'response-panel' as it prevents scrolling in Console 'Response' tab. r=nchevobbe

MozReview-Commit-ID: GHbYuCfs9L

--HG--
extra : rebase_source : 3daddc00d9e2cc724a3a68024514f64f8f49114e

The variables (basicShapeSVGBoxValues, etc.) in property_database.js are
moved to the beginning of the file so that they're defined before usage.

MozReview-Commit-ID: 7L3obIY1alP

--HG--
extra : rebase_source : 6c3dff5ecbdad8ef6cf1a49953e4ad1001620b6c

`MallocSizeOfOps::enclosing_size_of_op` is an `Option<>` type, and the panic in
question is caused by not providing a value in a case where it's needed for
measuring a HashSet.

HashMaps and HashSets are common enough that it makes sense to make
`enclosing_size_of_op` non-optional, which this patch does.

MozReview-Commit-ID: IB2aRuXHj8E

--HG--
extra : rebase_source : a6f593b718ca9e92a7a36ca7e2063a01e11c7e04

servo: Merge #18549 - Fix a panic in Stylo memory reporting (from nnethercote:fix-enclosing-crash); r=heycam

`MallocSizeOfOps::enclosing_size_of_op` is an `Option<>` type, and the panic in
question is caused by not providing a value in a case where it's needed for
measuring a HashSet.

HashMaps and HashSets are common enough that it makes sense to make
`enclosing_size_of_op` non-optional, which this patch does.

<!-- 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: -->
- [ ] There are tests for these changes OR
- [X] These changes do not require tests because tests are on the Gecko side.

<!-- 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: bb998dbdf31920d5ddc2a91d6bdfe8a880e11604

--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 18ff3083b36733a2a212f094f249b46872b4ec61

Continuation on bug 1397307 which was incomplete.

MozReview-Commit-ID: JGGHQyjnALI

--HG--
extra : rebase_source : 067652250dcd0904c8436eebc50068c7fb8d8cbb

Only the Windows H264 decoder supports CreateDecoderParam::mError, all the other PDM leave the value untouched.

As such, it can't be assumed that in case of failure, the mError attribute will be set.

MozReview-Commit-ID: GWHGP6Wv3fl

--HG--
extra : rebase_source : 081b71c7a53c41d9a13904e4182e3cfdb876ae43

MozReview-Commit-ID: JG9vo3dbMB

--HG--
extra : rebase_source : d699868284c5929aee3b26544fc99f454dd114ed

servo: Merge #18547 - style: Resolver cleanup and sharing by rule node fixes (from emilio:self-sharing); r=heycam

See the individual commits for details.

This is the only coherent story I have for crashes like:

  https://crash-stats.mozilla.com/report/index/bcdfe629-ca1f-4e4d-aa17-27f890170917

(And the fact that there are crashes like it on the main thread kinda indicates it's the case)

Source-Repo: https://github.com/servo/servo
Source-Revision: 2387dbedbb27629cd9e8c4657e8328ae04ff6d58

--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 2cebeca9acb1d40d2bc4eb3d2646f49ba24a3437

Also fixes a bad debug assertion

MozReview-Commit-ID: 5OV5KkvbRwZ

--HG--
extra : rebase_source : dbb41ecff52934f498b6d96b4cd174da246429f2

Because UBSan complains about casting -1:

> runtime error: load of value 4294967295, which is not a valid value for type 'nsCursor'

--HG--
extra : rebase_source : 037a96700228ea0d427afa7c25c40490c701cdc4

Bug 1400746 - checksums failure when boto3 and botocore present in our pypi mirrors, r=catlee DONTBUILD

MozReview-Commit-ID: 5MdNxr8TY8V

--HG--
extra : amend_source : 889cd0c5248669fb30c528770a56a013fd65bf69

Because UBSan complains about casting -1:

> runtime error: load of value 4294967295, which is not a valid value for type 'JSGCParamKey'

--HG--
extra : rebase_source : ff972b29f9a89fcbe50d9f105196bcd8f06486bd

MozReview-Commit-ID: Ek4onH23hPc

MozReview-Commit-ID: ExAoHf5iXNn

MozReview-Commit-ID: BVrawNPrB4h

Bug 1381638 - Change browser_devices_get_user_media_in_frame.js to test cam then cam+mic instead of mic then cam+mic, to avoid bug 1400488. r=ng

Summary: We're currently using the thread_rng to derive a cmd byte for the U2F protocol fuzzers. That of course should rather be derived deterministically from the input handed to the fuzzing target.

Bug #: 1400513

Differential Revision: https://phabricator.services.mozilla.com/D61

Bug #: 1400662

Differential Revision: https://phabricator.services.mozilla.com/D63

Backed out changeset 7d0893f1b6ce (bug 1389021) for leaking in mda2 on Linux x64 asan (bug 1374856). r=backout a=backout

MozReview-Commit-ID: AeaKVgSJTmt

Backed out changeset cc0acc00d769 (bug 1394233) for frequently failing own test usercss-uppercase.html on Windows 7 debug. r=backout a=backout

MozReview-Commit-ID: GwVKJKGPzDS

MozReview-Commit-ID: 9APhbRHIMUP

--HG--
extra : rebase_source : 5f62596fab23c2b832d6cdb85764f3b4b37aa7ad

servo: Merge #18540 - Use BluetoothAdapter mock when bluetooth is disabled (from paulrouget:no_bt); r=nox

Today, only the DOM API is disabled.
When bluetooth is disabled, can we also disable bluetooth device code?

Source-Repo: https://github.com/servo/servo
Source-Revision: 06628d2f6090e069b3447ad1ff09a1158e0836ab

--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 3e6d03cd191932346385b0ee89c99277ef1d0bd7

The previous drag space was only set as min-height on the titlebar,
which led tabsintitlebar.js to not account that extra space for moving
the titlebar to the bottom (because it calculates that height from
tab strip height). So while it looked fine visually, the titlebar did
not stretch all the way to the bottom, so that e.g. double-clicks aren't
registered correctly.

MozReview-Commit-ID: 1mHFDBUe3sC

--HG--
extra : rebase_source : 667b131485658927fc2f3d484b2ab15cce782d95

This patch changes the test_construction.html with following modification.
1. Modify the test testWithDuplicateShippingOptionsParameters to expect a
   TypeError when constructing wiht duplicate shippingOption ids.
2. Add test testShippingOtpionAttribute for shippingOption setting checking
   with following conditions
   1. No selected shippingOption and PaymentOptions.requestShipping is false
   2. One selected shippingOption and PaymentOptions.requestShipping is false
   3. One selected shippingOption and PaymentOptions.requestShipping is true
   4. Multiple selected shippingOptions and PaymentOptions.requestShipping is
      true.

This patch implements the following changes according to the spec change.
See https://w3c.github.io/payment-request/#constructor step 8 for more
details.

1. Return TypeError during PaymentRequest construction with duplicate
   shippingOption id.
2. Set PaymentRequest.shippingOption with the selected shippingOption only
   if options.requestShipping is true.

Bug 1381157 - Cache 'mContent->GetPrimaryFrame == this' with a flag on nsIFrame and replace these calls to GetPrimaryFrame. r=mats

MozReview-Commit-ID: 3VoxYlean52

MozReview-Commit-ID: 7AY4eGIOdv