Bug 1322570 Part 4 - Use GetParentAllowServo() in KeyframeEffectReadOnly::UpdateProperties. Per bug 1322570 Comment 7, we could drop the GetParentAllowServo() when we invoke UpdateProperties() from a SquentialTask, so allow it for now. MozReview-Commit-ID: 52NauGaz4Zv

Bug 1322570 Part 3 - Get StyleContext from parent frame in nsFlexContainerFrame::Init(). In stylo, nsStyleContext::GetParent() is not valid. MozReview-Commit-ID: 5FbgUwobG3U

Bug 1322570 Part 2 - Resolve {align,justify}-self using StyleContext from alignment container frame in ReflowInput::InitConstraints(). Per bug 1322570 comment 46, it's not easy to replace ComputedJustifyItems() and UsedJustifySelf()'s internal nsStyleContext::GetParent() without correctness penalty, so we use GetParentAllowServo() for now. Also, fix the reftest.list added in bug 1334403 which incorrectly wrote test page as reference page. MozReview-Commit-ID: 6kAAWSFojd5

Bug 1322570 Part 1 - Add MOZ_ASSERT in nsStyleContext::GetParent() to disallow usage by stylo. Also, add GetParentAllowServo() to whitelist the usage in servo-backed style system in subsequent parts so that we could revisit them later. MozReview-Commit-ID: JthU18Ftx02

Bug 1347336 - Display grid line name and numbers in Grid Highlighter. r?gl MozReview-Commit-ID: Eh7GEYYZyqc

Aspect ratio patch MozReview-Commit-ID: BRljeUNHg98

Throttle grid highlight event MozReview-Commit-ID: EGzJXFdnLzH

Bug 1339004 - Do DocGroup labeling in dom/security MozReview-Commit-ID: 92LLqMOeTmF

Bug 1343754 - Label PLayerTransaction. r?bevistseng, kats MozReview-Commit-ID: 7hgt9dqzbyq

Bug 1343754 - Label PTexture. r?bevistseng, kats MozReview-Commit-ID: 1PnDEQvz9FK

Bug 1349989: Correctly handle errors for OMT-compiled scripts. r?shu MozReview-Commit-ID: 3FpoUmu9ijI

Bug 1346607: Follow-up: Fix intermittent failure on Windows. r=me MozReview-Commit-ID: 9tfJ4ekq7BR

Bug 1348442: Part 4 - Remove support for synchronously loading localized extension CSS. r=jdm After switching to loading content stylesheets asynchronously, there are no longer any consumers that require a synchronous channel to load localized CSS, so these workarounds are no longer necessary. MozReview-Commit-ID: AwLSmYf9qL3

Bug 1348442: Part 3 - Do not evict cached stylesheets while they're still being used by extant documents. r=aswan There are some optimizations, both existing and under way, that allow us to share some stylesheet data between documents that they're loaded into. Keeping cached sheets around as long as they're still in use should be a net memory savings. MozReview-Commit-ID: HUZzs6HhuFM

Bug 1348442: Part 2c - Refactor Script class into ES6 class. r=aswan MozReview-Commit-ID: Dtci1mfQts0

Bug 1348442: Part 2b - Add getWinUtils helper. r=aswan MozReview-Commit-ID: 9vvCbYovyoN

Bug 1348442: Part 2a - Asynchronously load and cache content script CSS. r=aswan MozReview-Commit-ID: 1BzLNbdXMfU

Bug 1348442: Part 1 - Allow loading preloaded stylesheets asynchronously. r=heycam These changes allow us to asynchronously load pre-loaded stylesheets, in a way that's similar to ChromeUtils.compileScript. The new method returns a Promise which resolves to the preloaded sheet once it's finished loading. This will allow us to remove the last remaining use of synchronous channels in moz-extension: URLs. MozReview-Commit-ID: 7J52ff93YKT

Bug 1349138 Edit transactions should store their editor instance with strong reference r=smaug Edit transactions should store their editor instance with strong reference and they should be released at destroying the editor. MozReview-Commit-ID: D67KU8WFxyo

Bug 1315850 - Ask the GMPService for the GMP thread in GMPParent::ChildTerminated. r=gerald When we shutdown the browser while the GMPService is active we can end up leaking a GMPParent, GeckoMediaPluginServiceParent, and a Runnable. I tracked this down to the runnable dispatched to the GMP thread in GMPParent::ChildTerminated(). The dispatch of this runnable is failing as we are dispatching the runnable to a reference of the GMP thread which we have previously acquired, but that thread is now shutdown. So the dispatch fails, and if you look in nsThread::DispatchInternal() you'll see that we deliberately leak the runnable if dispatch fails! The runnable leaking means that the references it holds to the GMPParent and the GMP service parent leak. The solution in this patch is to not cache a reference to the GMP thread on the GMPParent; instead we re-request the GMP thread from the GMPService when we want it. This means that in the case where the browser is shutting down, GMPParent::GMPThread() will return null, and we'll not leak the runnable. We'll then follow the (hacky) shutdown path added in bug 1163239. We also need to change GMPParent::GMPThread() and GMPContentParent::GMPThread() to return a reference to the GMP thread with a refcount held on it, in order to ensure we don't race with the GMP service shutting down the GMP thread while we're trying to dispatch to in on shutdown. MozReview-Commit-ID: CXv9VZqTRzY