Bug 1383065 - Consider the form with 3 address fields as a valid address form. r=lchang MozReview-Commit-ID: Ck81HbI3zwe

Bug 1275878 - Part 2: Replace places-will-close-connection notification with a shutdown blocker. r=adw MozReview-Commit-ID: A2sn2OreX4K

Bug 1275878 - Part 1: move back clear history operations to History.clear(). r=adw MozReview-Commit-ID: DbEJgKbTxd7

Bug 1383001: Yet another crashtest. r=heycam MozReview-Commit-ID: 1B0IloRjVha

Bug 1383001: Crashtests for this and bug 1383319. r=heycam MozReview-Commit-ID: CDWKn1ygZ6S

servo: Merge #17834 - stylo: Fix the interaction of frame construction restyles with animation restyles (from emilio:animation-fc-crash); r=heycam Fixes bug 1383001. Source-Repo: https://github.com/servo/servo Source-Revision: 30d6d6024bd0a082424395621f620dc9580970e5

Bug 1359855 - Prevent loading DevTools when saving session restore data. r=jdescottes,mossop MozReview-Commit-ID: 1d7WmiGRSmp

Bug 1359855 - Remove assertion for dynamic key registration. r=jdescottes Per definition of this bug/patch, key shortcuts can't be registered anymore. It mostly means that add-on definition a key shortcut won't keep their key shortcut working. This shouldn't be an issue on 57 as I don't think WebExtension addon can set a key shortcut via this DevTools API. MozReview-Commit-ID: G5c8JzaUWoR

Bug 1359855 - Update key id reference if tests for responsive design. r=jdescottes MozReview-Commit-ID: JJxo8R3mkOA

Bug 1359855 - Fix support of per tool key shortcuts in toolboxes opened in a window. r=jdescottes MozReview-Commit-ID: kP07KzpzxI

Bug 1359855 - Inline jsonview main module to keep it working before user action. r=Honza,jdescottes MozReview-Commit-ID: 3COOvQtYn0E

Bug 1359855 - Fix the developer toggle in customize widgets. r=jdescottes Now that devtools-browser is lazily evaluated, we have to create the widget early in devtools-startup. MozReview-Commit-ID: JanbAPalYE1

Bug 1359855 - Prevent loading any DevTools module until users interact with any devtool entrypoint. r=jdescottes MozReview-Commit-ID: 4rORySoFRQY

Bug 1377740 - Only set the url when the link exists n?nechen r=nechen MozReview-Commit-ID: AqChrNYGChw

Bug 1383056 - Disable unstable elementFromPoint test on win 10, r=Tomcat MozReview-Commit-ID: 9ulmYUYpbdr

Bug 1383580 - Pad estimated CDM frame sizes. r=gerald The new video decoder in CDM version 1.4.8.970 seems to calculate its frame size as about 1.5X of the optimal size. So increase our estimate of CDM video frame buffer sizes by more than that so that our pre-allocated buffers should be big enough to accomodate the allocations that the CDM requests. This means we should be more likely to avoid the slow fallback path where we have to transfer frames from the CDM to the content process using the non-shmem path. MozReview-Commit-ID: 6PT8XVCAL3E

Bug 1383580 - Add an explicit message to increase CDM-Firefox shmem pool. r=gerald The strategy we were using to expand the pool of shmems we use to shuffle video frames between the CDM and content processses is to increase the size of the pool if the content process receives a video frame in a non-shmem. However the CDM process will send a frame in a non-shmem if none of the shmems in the pool are big enough to fit the frame the CDM produces. This happens if we underestimate the size required for video frames. This causes the ChromiumCDMParent to increase the number of shmems in the pool every time we rate switch, until we eventually hit the limit of 50, whereupon playback fails. So we need to disambiguate between these two cases; the first being we have a pool of shmems, but they're the wrong size, the second being our shmems are the right size, but we've run out and we need to expand the shmem pool. The only place where we know this is in the CDM process. So this commit adds a new message to PChromiumCDM through which the ChromiumCDMChild can report to the parent that it needs more shmems in the pool. The new Widevine CDM has a new video decoder which allocates video frames less optimally than the previous, which causes us to hit this more often in Nightly. Our telemetry also indicates we hit this rarely in Beta with the old CDM. MozReview-Commit-ID: LoSvVhxHQxn

Bug 1319407 - Add reftest for box-decoration-break with clip-path. r=cjku MozReview-Commit-ID: CSkM3e15jIK

Bug 1319407 - Apply clip-path to each frame when box-decoration-break is clone. r=cjku,heycam MozReview-Commit-ID: E7IR49MzkWm

servo: Merge #17831 - Iterate through properties in priority order when computing keyframes (from birtles:property-priorities); r=heycam This is largely just a translation of Gecko's PropertyPriorityIterator[1] into rust with the exception that IDL sort order is only defined for shorthands since that's all we currently require. [1] http://searchfox.org/mozilla-central/rev/3a3af33f513071ea829debdfbc628caebcdf6996/dom/animation/KeyframeUtils.cpp#151 --- <!-- 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 --stylo` does not report any errors - [x] These changes fix (Gecko bug 1371493)[https://bugzilla.mozilla.org/show_bug.cgi?id=1371493]. - [x] There are tests for these changes OR <!-- 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: a47fde038e893d4b76d64b6917085d8e5bc9d8d1