0a824e644bfbb7c00ed89253026021c15d00f39e: Bug 1368496 - Add support for fixed-positioning with APZ. r=jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 07 Jun 2017 09:54:10 -0400 - rev 590286
Push 62677 by kgupta@mozilla.com at Wed, 07 Jun 2017 14:43:07 +0000
Bug 1368496 - Add support for fixed-positioning with APZ. r=jrmuizel This implements at least enough fixed-positioning support to make the reftest in layout/reftests/async-scrolling/bg-fixed-child.html pass. That test implements a simple background-attachment:fixed which is implemented in the layer tree with a combination of a scrolled clip and a fixed-position layer. Previous patches in this patchset implemented support for the scrolled clip, and this patch implements the fixed-position layer support. MozReview-Commit-ID: 1Al1YshhUL7
634529a7d3b696c350d7a6728558bd3ab0070a41: Bug 1368496 - Expose the push_clip_and_scroll_info API in WR via WebRenderAPI. r=jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 07 Jun 2017 09:54:09 -0400 - rev 590285
Push 62677 by kgupta@mozilla.com at Wed, 07 Jun 2017 14:43:07 +0000
Bug 1368496 - Expose the push_clip_and_scroll_info API in WR via WebRenderAPI. r=jrmuizel MozReview-Commit-ID: f8gIDoUDC1
f82394d7b131bd5d7b03d99e78be002c8a563a03: Bug 1368496 - Track the pushed clip and scroll IDs. r=jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 07 Jun 2017 09:54:09 -0400 - rev 590284
Push 62677 by kgupta@mozilla.com at Wed, 07 Jun 2017 14:43:07 +0000
Bug 1368496 - Track the pushed clip and scroll IDs. r=jrmuizel Tracking the active clips and scroll layers is helpful for implementing fixed-position type stuff, because we will need to answer questions like "what is the ancestor scroll layer of this other scroll layer that is somewhere on the stack" and "what is the currently active stack of non-scrolling clips". This patch also adds a couple of methods to WebRenderAPI that answers questions like these. MozReview-Commit-ID: 9bgOW3Z8Tbp
013150c081c97fb0635a895af3bb6f7c29439874: Bug 1368496 - Propagate the layer's "scrolled clip" to WebRender. r=jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 07 Jun 2017 09:54:09 -0400 - rev 590283
Push 62677 by kgupta@mozilla.com at Wed, 07 Jun 2017 14:43:07 +0000
Bug 1368496 - Propagate the layer's "scrolled clip" to WebRender. r=jrmuizel If the layer has a "scrolled clip", that clip scrolls with the content of the layers (it moves if any of the scrollable frames defined by that layer are scrolled). MozReview-Commit-ID: 37hvXWO930f
3abcf2e0c9da8dee6d7c3b650369f6bab86960e6: Bug 1368496 - Skip over scrollinfo layers instead of aborting entirely. r?jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 07 Jun 2017 09:54:09 -0400 - rev 590282
Push 62677 by kgupta@mozilla.com at Wed, 07 Jun 2017 14:43:07 +0000
Bug 1368496 - Skip over scrollinfo layers instead of aborting entirely. r?jrmuizel MozReview-Commit-ID: 5pYcurXfAf
56f67d9d673d608e801d018836f8613de3b2032c: Bug 1368496 - Extract a helper function from WebRenderLayer::ClipRect(). r?jrmuizel draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 07 Jun 2017 09:54:08 -0400 - rev 590281
Push 62677 by kgupta@mozilla.com at Wed, 07 Jun 2017 14:43:07 +0000
Bug 1368496 - Extract a helper function from WebRenderLayer::ClipRect(). r?jrmuizel No functional changes, but we'll want this helper in a future patch for code reuse. MozReview-Commit-ID: IQEJq2o1UI0
73cd9a01eb689b2c13e192cbd04363e37347d1f3: Bug 1366755 - devtools.panels.create should set invertIconForLighttheme to false by default. draft
Luca Greco <lgreco@mozilla.com> - Wed, 07 Jun 2017 16:34:56 +0200 - rev 590280
Push 62676 by luca.greco@alcacoop.it at Wed, 07 Jun 2017 14:40:15 +0000
Bug 1366755 - devtools.panels.create should set invertIconForLighttheme to false by default. MozReview-Commit-ID: 1bn3cMngoql
19074b75203bde71127fea4cd461360729e1d803: Bug 1370242 - Prevent performance data from being uploaded when collecting code coverage. r?jmaher draft
Greg Mierzwinski <gmierz2@outlook.com> - Wed, 07 Jun 2017 10:35:04 -0400 - rev 590279
Push 62675 by bmo:gmierz2@outlook.com at Wed, 07 Jun 2017 14:35:55 +0000
Bug 1370242 - Prevent performance data from being uploaded when collecting code coverage. r?jmaher This patch is to prevent performance data from being collected when code coverage is running. It uses the environment variables that are set when code coverage is being collected to detect when it shouldn't gather the data. MozReview-Commit-ID: 777vfmwYbe0
bb43a7b82922781752807d964e53e6125e32a3e9: Bug 1370805: P3. Use whichever extradata is available when constructing the decoder. r?jwwang draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 07 Jun 2017 15:14:57 +0200 - rev 590278
Push 62674 by bmo:jyavenard@mozilla.com at Wed, 07 Jun 2017 14:33:29 +0000
Bug 1370805: P3. Use whichever extradata is available when constructing the decoder. r?jwwang Prior bug 1313398, the only time we would call H264Converter::CreateDecoderAndInit was if we encountered AVC3 content where the H264 extradata didn't exist in the metadata. AVC3 was the only situation where mDecoder would be null after construction. However, now, it is possible for the construction of the decoder to be interrupted, which would leave mDecoder null. For AVC1 content, if this happened, we wouldn't have in-band SPS/PPS necessary for CreateDecoderAndInit to complete. So we use whichever extradata is available. MozReview-Commit-ID: 702xj045LAv
969ddfab2eb1d79a7861bfe2dc7a505ec1148368: Bug 1370805: P2. Let current operation completes before continuing. r?jwwang draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 07 Jun 2017 15:10:04 +0200 - rev 590277
Push 62674 by bmo:jyavenard@mozilla.com at Wed, 07 Jun 2017 14:33:29 +0000
Bug 1370805: P2. Let current operation completes before continuing. r?jwwang This is a simpler approach required as both InitPromise and FlushPromise are exclusives. It's in practice simpler too. MozReview-Commit-ID: ItaAhC0Bk8T
634a40cf4ac441b87c51345c2da5637cad23628a: Bug 1370805: P1. Revert "Bug 1370164: Properly handle flushing during ongoing operations. r=jwwang" r?jwwang draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 07 Jun 2017 13:32:09 +0200 - rev 590276
Push 62674 by bmo:jyavenard@mozilla.com at Wed, 07 Jun 2017 14:33:29 +0000
Bug 1370805: P1. Revert "Bug 1370164: Properly handle flushing during ongoing operations. r=jwwang" r?jwwang
614a10e59bfddda7452281f3a00eb04823ad6c65: Bug 1355048: P1. Have WebrtcMediaDataDecoder placeholder. r?jesup draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Mon, 10 Apr 2017 20:40:31 +0200 - rev 590275
Push 62674 by bmo:jyavenard@mozilla.com at Wed, 07 Jun 2017 14:33:29 +0000
Bug 1355048: P1. Have WebrtcMediaDataDecoder placeholder. r?jesup The code currently does nothing. MozReview-Commit-ID: 6C0sLKIoJEV
0eafa9aa223a51609573c8e48a367552f13a97e6: bug 1369531 - Collect INPUT_EVENT_RESPONSE_COALESCED_MS opt-out r?Dexter r?bsmedberg draft
Chris H-C <chutten@mozilla.com> - Wed, 07 Jun 2017 10:14:41 -0400 - rev 590274
Push 62673 by bmo:chutten@mozilla.com at Wed, 07 Jun 2017 14:14:53 +0000
bug 1369531 - Collect INPUT_EVENT_RESPONSE_COALESCED_MS opt-out r?Dexter r?bsmedberg MozReview-Commit-ID: I8hmmfLYCxt
113a1304b22ea10e1c24351dcd79c06f078cabfc: Bug 1265526 - Correctly categorize blob URLs and wasm frames as user content; r?julienw draft
Greg Tatum <tatum.creative@gmail.com> - Fri, 26 May 2017 18:07:56 -0500 - rev 590273
Push 62672 by bmo:gtatum@mozilla.com at Wed, 07 Jun 2017 14:09:45 +0000
Bug 1265526 - Correctly categorize blob URLs and wasm frames as user content; r?julienw asm.js and wasm frames were not being correctly identified as user content in the perf devtool. This patch correctly finds blob urls that were being mis-identified as platform content, and wasm frames, which do not have any identifying information other than their function name containing wasm-function. MozReview-Commit-ID: 4DjqATCKBK0
ab5ca9b9cef0c6d4fbacdcf92ff74df0ad8be024: Bug 1357082 - Retry synthesizeMouseAtCenter until it is performed. r?xidorn draft
Greg Mierzwinski <gmierz2@outlook.com> - Tue, 06 Jun 2017 09:22:36 -0400 - rev 590272
Push 62671 by bmo:gmierz2@outlook.com at Wed, 07 Jun 2017 14:03:02 +0000
Bug 1357082 - Retry synthesizeMouseAtCenter until it is performed. r?xidorn This patch is for the intermittent bug 1357082 which has a failure in the test 'test_pointerlock-api.html' and is more frequent when it is run on Ubuntu 16.04. This failure is resolved by retrying the mouse movement until it actually occurs. MozReview-Commit-ID: 9XC4zmWj8Gn
e1edb1c14a6402ee01d2c28b4445531ad3f7b51f: Bug 1364535 - Devtools frontend WebAssembly support for source maps and wast. r?jlast draft
Yury Delendik <ydelendik@mozilla.com> - Tue, 06 Jun 2017 20:11:00 -0500 - rev 590271
Push 62670 by ydelendik@mozilla.com at Wed, 07 Jun 2017 13:43:22 +0000
Bug 1364535 - Devtools frontend WebAssembly support for source maps and wast. r?jlast MozReview-Commit-ID: KEkXaAQCWYN
a295f16062d4d441ca9324455bf895aa6e61129a: Bug 1364535 - Devtools frontend WebAssembly support for source maps and wast. draft
Yury Delendik <ydelendik@mozilla.com> - Tue, 06 Jun 2017 20:11:00 -0500 - rev 590270
Push 62669 by ydelendik@mozilla.com at Wed, 07 Jun 2017 13:42:23 +0000
Bug 1364535 - Devtools frontend WebAssembly support for source maps and wast. MozReview-Commit-ID: KEkXaAQCWYN
989b23024aac2bab29978784a7523fca89fd7f22: Bug 1370850 - Serialise undefined script evaluation return value to null; r?maja_zf draft
Andreas Tolfsen <ato@mozilla.com> - Wed, 07 Jun 2017 12:46:14 +0100 - rev 590269
Push 62668 by bmo:ato@mozilla.com at Wed, 07 Jun 2017 13:32:21 +0000
Bug 1370850 - Serialise undefined script evaluation return value to null; r?maja_zf When a call through the content frame proxy is interrupted by the dialogueObserver, the synchronous promise that is meant to wait for a response from the frame script is resolved immediately with an undefined return value. When an undefined value is assigned to the response body, it gets dropped during JSON serialisation. To ensure the "value" field expected from the Execute Script and Execute Async Script commands is populated, we need to assign a null value to resp.body.value. We can treat undefined as null by calling evaluate.toJSON again on the return value from the proxied frame script call. This effectively means we serialise it twice, since it first needs to be serialised to cross the IPC border, though the second computation only looks at primitives and no known web element store is required. It would be nicer if the content frame script itself would be able to return early with null by installing a user prompt notification event, but this is not possible because the tabmodal dialogue that appears blocks script execution. This means we need to rely on the dialogueObserver in testing/marionette/proxy.js to take care of the dialogue for us. MozReview-Commit-ID: D14TA2TYYXI
7691355fd89aa399b3833a3ef87298590f202dfe: Bug 1370871 - Remove "global" global from evaluate script context; r?automatedtester draft
Andreas Tolfsen <ato@mozilla.com> - Wed, 07 Jun 2017 14:24:24 +0100 - rev 590268
Push 62667 by bmo:ato@mozilla.com at Wed, 07 Jun 2017 13:25:42 +0000
Bug 1370871 - Remove "global" global from evaluate script context; r?automatedtester Marionette exposes a global called "global" to scripts that are evaluated in sandboxes. This is no longer needed after the rewrite of the testing/marionette/evaluate.js module. MozReview-Commit-ID: BobdwilaCy0
0d90915ecf319b94e1e80e9fca96e1f545895bcf: Bug 1293298 - Implement events in SubTypes defined in the WebExtensions API schema files. draft
Luca Greco <lgreco@mozilla.com> - Thu, 01 Jun 2017 20:02:54 +0200 - rev 590267
Push 62666 by luca.greco@alcacoop.it at Wed, 07 Jun 2017 13:19:58 +0000
Bug 1293298 - Implement events in SubTypes defined in the WebExtensions API schema files. MozReview-Commit-ID: CAYaenfSih1
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip