Bug 1314177 - remove redundancy in install location classes r?aswan MozReview-Commit-ID: H4dTeU3N8zI

Bug 1353929 - Enable new Chromium Widevine IPC protocol. r?gerald This gives us simpler code, and eliminates some extra frame copies. MozReview-Commit-ID: 10N0O9Pn0Kw

Bug 1353929 - Enable new Chromium Widevine IPC protocol. r?gerald This gives us simpler code, and eliminates some extra frame copies. MozReview-Commit-ID: 10N0O9Pn0Kw

Bug 1351953 - Pre-allocate shmems for the CDM process to use for storing decrypted and audio samples. r=gerald Makes transfer of samples between the content and CDM processes use shmems. The Chromium CDM API requires us to implement a synchronous interface to supply buffers to the CDM for it to write decrypted samples into. We want our buffers to be backed by shmems, in order to reduce the overhead of transferring decoded frames. However due to sandboxing restrictions, the CDM process cannot allocate shmems itself. We don't want to be doing synchronous IPC to request shmems from the content process, nor do we want to have to do intr IPC or make async IPC conform to the sync allocation interface. So instead we have the content process pre-allocate a set of shmems and give them to the CDM process in advance of them being needed. When the CDM needs to allocate a buffer for storing a decrypted sample, the CDM host gives it one of these shmems' buffers. When this is sent back to the content process, we copy the result out (uploading to a GPU surface for video frames), and send the shmem back to the CDM process so it can reuse it. We predict the size of buffer the CDM will allocate, and prepopulate the CDM's list of shmems with shmems of at least that size, plus a bit of padding for safety. We pad frames out to be the next multiple of 16, as we've seen some decoders do that. Normally the CDM won't allocate more than one buffer at once, but we've seen cases where it allocates two buffers, returns one and holds onto the other. So the minimum number of shmems we give to the CDM must be at least two, and the default is three for safety. MozReview-Commit-ID: 5FaWAst3aeh

Bug 1351953 - Make DecryptJob::PostResult take a mozilla::Span instead of nsTArray. r=gerald This means we can pass anything that converts implicitly to a Span to PostResult, including an nsTArray<uint8_t>. We can also pass a Span that contains the contents of a Shmem's buffer. MozReview-Commit-ID: 8AAcRmVCEVy

Bug 1351953 - Send Data to CDM for decrypt and or decode in shmems. r=gerald MozReview-Commit-ID: 2UdGimoOLKr

Bug 1323036 - Preserve case of header names MozReview-Commit-ID: 2jDHOr2GI6T

Bug 1351953 - Pre-allocate shmems for the CDM process to use for storing decrypted and audio samples. r=gerald Makes transfer of samples between the content and CDM processes use shmems. The Chromium CDM API requires us to implement a synchronous interface to supply buffers to the CDM for it to write decrypted samples into. We want our buffers to be backed by shmems, in order to reduce the overhead of transferring decoded frames. However due to sandboxing restrictions, the CDM process cannot allocate shmems itself. We don't want to be doing synchronous IPC to request shmems from the content process, nor do we want to have to do intr IPC or make async IPC conform to the sync allocation interface. So instead we have the content process pre-allocate a set of shmems and give them to the CDM process in advance of them being needed. When the CDM needs to allocate a buffer for storing a decrypted sample, the CDM host gives it one of these shmems' buffers. When this is sent back to the content process, we copy the result out (uploading to a GPU surface for video frames), and send the shmem back to the CDM process so it can reuse it. We predict the size of buffer the CDM will allocate, and prepopulate the CDM's list of shmems with shmems of at least that size, plus a bit of padding for safety. We pad frames out to be the next multiple of 16, as we've seen some decoders do that. Normally the CDM won't allocate more than one buffer at once, but we've seen cases where it allocates two buffers, returns one and holds onto the other. So the minimum number of shmems we give to the CDM must be at least two, and the default is three for safety. MozReview-Commit-ID: 5FaWAst3aeh

Bug 1351953 - Make DecryptJob::PostResult take a mozilla::Span instead of nsTArray. r=gerald This means we can pass anything that converts implicitly to a Span to PostResult, including an nsTArray<uint8_t>. We can also pass a Span that contains the contents of a Shmem's buffer. MozReview-Commit-ID: 8AAcRmVCEVy

Bug 1351954 - Send Data to CDM for decrypt and or decode in shmems. r=gerald MozReview-Commit-ID: 2UdGimoOLKr

Bug 1323036 - Preserve case of header names MozReview-Commit-ID: 2jDHOr2GI6T

Bug 812687 part 9: Add tests for "order" property's influence on list-numbering, baseline, and focus order in a flexbox. (no review, test-only) MozReview-Commit-ID: EEkPlCgzknG

Bug 812687 part 9: Add tests for "order" property's influence on list-numbering, baseline, and focus order in a flexbox. (no review, test-only) MozReview-Commit-ID: EEkPlCgzknG

Bug 812687 part 8: Add a test for "order" on flex items with abspos siblings. r=mats MozReview-Commit-ID: aCBQER5r2G

Bug 1353921 - Make letter-spacing animatable. r?emilio From the spec: 'normal' value computes to zero. MozReview-Commit-ID: Yq13q3WDkm

Bug 1336763 - [WIP] Add a beforeunload event handler count to TabChild. MozReview-Commit-ID: 8b0gBYWwMDn

Bug 1322044 - Only mark a subdomain cached when includeSubDomains is true r?keeler,ckerschb MozReview-Commit-ID: 3lFkuLauyGg

Bug 1346256 Part 3: Modify GetCSSStyleRules to collect ServoStyleRules. MozReview-Commit-ID: IMQLykuXjfL

Bug 1346256 Part 2: Define methods in ServoCSSRuleList to fill a hash of RawServoStyleRule to ServoStyleRule. MozReview-Commit-ID: 4Swb9KwV0uO

Bug 1346256 Part 1: Add FFI interfaces for exposing style sources. MozReview-Commit-ID: FOQCgXD68E9