1a429aa9abdb7a4cc9165d52e8b4844559785001: Bug 1399693 - Update the watermark Firefox logo used on new tab from png to svg, r=gasolin
Fischer.json <fischer.json@gmail.com> - Fri, 15 Sep 2017 14:38:16 +0800 - rev 665686
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1399693 - Update the watermark Firefox logo used on new tab from png to svg, r=gasolin MozReview-Commit-ID: 2GvFoTC1MtN
c56a205100ac8747670ad5ad5ba1d6c66ce77310: Bug 1399615 - Export Screenshots 19.0.0 to Firefox r=kmag
Ian Bicking <ianb@colorstudy.com> - Wed, 13 Sep 2017 14:40:39 -0500 - rev 665685
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1399615 - Export Screenshots 19.0.0 to Firefox r=kmag MozReview-Commit-ID: 1QFbWCThVeg
1256cadba71bc9e0677e4f92174bc76ad8952eb5: Bug 1399796 - UnsubmittedCrashHandler should never check for unsubmitted crash reports if disabled or suppressed. r=Felipe
Mike Conley <mconley@mozilla.com> - Fri, 15 Sep 2017 09:25:04 -0700 - rev 665684
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1399796 - UnsubmittedCrashHandler should never check for unsubmitted crash reports if disabled or suppressed. r=Felipe Bug 1355492 moved the logic for scanning for unsubmitted crash reports out of the initialization of UnsubmittedCrashHandler, and the initialization is what decided whether or not it was appropriate to scan in the first place. This was done so that scanning could be deferred until idle after first paint. This patch makes it so that the scanning logic first ensures that the UnsubmittedCrashHandler is actually enabled and not suppressed (which is calculated earlier). I've also taken the liberty of adding a regression test. MozReview-Commit-ID: 3Aihom5Q17R
18dad63ef0c67b7bc0e8afb4c1268d5d6c30a55b: Bug 1400129 Remove unused accessKey l10n property r=flod
Andrew Swan <aswan@mozilla.com> - Fri, 15 Sep 2017 09:50:08 -0700 - rev 665683
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1400129 Remove unused accessKey l10n property r=flod MozReview-Commit-ID: 3K5Mt2blZgl
8998495d56dcb03aac5376b72ccd73ab19dbfc8c: Bug 1399511 - Update message displayed when a section has no data in about:telemetry r=chutten
Francesco Lodolo (:flod) <flod@lodolo.net> - Fri, 15 Sep 2017 06:53:33 +0200 - rev 665682
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1399511 - Update message displayed when a section has no data in about:telemetry r=chutten MozReview-Commit-ID: 2Hb4oKKlhG7
f73a6867afeead095c1804adb63815fb885af2f3: Bug 1398820 - Do not add duplicate rtp extensions; r=bwc
Dan Minor <dminor@mozilla.com> - Thu, 14 Sep 2017 15:55:33 -0400 - rev 665681
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1398820 - Do not add duplicate rtp extensions; r=bwc MozReview-Commit-ID: G6wLXW7z05d
880d772e282e47a015605622ca0046569c80bd71: Bug 1399592 - Increase Marionette startup timeout for mochitest/reftest. r=gbrown
Henrik Skupin <mail@hskupin.info> - Thu, 14 Sep 2017 16:18:58 +0200 - rev 665680
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1399592 - Increase Marionette startup timeout for mochitest/reftest. r=gbrown Currently the mochitest and reftest runners are forcing a timeout of 60s (or 900s for valgrind or debug builds) when calling `start_session` of Marionette. While this method still offers a timeout parameter, the timeout should be set via the `startup_timeout` argument for Marionette. Reason is that Marionette doesn't control the browser instance and is getting called right after the application gets launched. As such slow running builds can cause timeouts once it takes longer than 60s for the Marionette server to get started. By using `startup_timeout` the timeout will even be configurable via the command line and mozharness config files. MozReview-Commit-ID: EV7GklBcJjU
26275c18b48c2aa4e64e8bb54062469fb63c0296: Bug 1391605 - Bump geckodriver to 0.19.0. r=ato
Henrik Skupin <mail@hskupin.info> - Thu, 14 Sep 2017 18:08:28 +0200 - rev 665679
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1391605 - Bump geckodriver to 0.19.0. r=ato MozReview-Commit-ID: 4ai3ShcNhdS
7f5db3c919582c4b8fdbf35007b48d0005fd3007: Bug 1391605 - Update CHANGES.md for changes in geckodriver 0.19.0. r=ato
Henrik Skupin <mail@hskupin.info> - Thu, 14 Sep 2017 18:06:43 +0200 - rev 665678
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1391605 - Update CHANGES.md for changes in geckodriver 0.19.0. r=ato MozReview-Commit-ID: D1AAN8iWsuP
a35cf697567ab04735f1def1b399c03f40f35f39: Bug 1394461 - Update illustration and copy for about:rights. ui-r=shorlander r=dao
Erica Wright <ewright@mozilla.com> - Thu, 31 Aug 2017 11:20:11 -0400 - rev 665677
Push 80148 by bmo:emilio@crisal.io at Fri, 15 Sep 2017 20:59:22 +0000
Bug 1394461 - Update illustration and copy for about:rights. ui-r=shorlander r=dao MozReview-Commit-ID: 3kxO8DYG6R8
5cc01a58630f7d13eb5b13b0cd3b67532170a594: Bug 1400394 - Remove `TestingUtils.deepCopy`. r?markh draft
Kit Cambridge <kit@yakshaving.ninja> - Fri, 15 Sep 2017 13:46:21 -0700 - rev 665676
Push 80147 by bmo:kit@mozilla.com at Fri, 15 Sep 2017 20:53:48 +0000
Bug 1400394 - Remove `TestingUtils.deepCopy`. r?markh MozReview-Commit-ID: 3ZZpA3inWSF
c265b7e884e2cff475b3db8bf9e67b5a42ae97a2: Bug 1400387 - Change 32-bit VR Frame ID's to 64-bit draft
Kearwood "Kip" Gilbert <kgilbert@mozilla.com> - Fri, 15 Sep 2017 13:38:47 -0700 - rev 665675
Push 80146 by kgilbert@mozilla.com at Fri, 15 Sep 2017 20:49:14 +0000
Bug 1400387 - Change 32-bit VR Frame ID's to 64-bit MozReview-Commit-ID: BSvZMa0XVSO
66510c5e8690f2d45f3f17a8cdfffaf715d5cefa: Bug 1400034 - Turn on layers-free for transform/ and transform-3d/ reftests. r?ethlin,pchang draft
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 15 Sep 2017 16:44:49 -0400 - rev 665674
Push 80145 by kgupta@mozilla.com at Fri, 15 Sep 2017 20:45:37 +0000
Bug 1400034 - Turn on layers-free for transform/ and transform-3d/ reftests. r?ethlin,pchang MozReview-Commit-ID: LvU3kT4rJCK
85796dfd0f59c74794598bd186d2c5cab87604d1: Bug 1394457 - Update illustration for about:sessionrestore. ui-r=shorlander, r?dao draft
Erica Wright <ewright@mozilla.com> - Fri, 08 Sep 2017 11:57:18 -0400 - rev 665673
Push 80144 by bmo:ewright@mozilla.com at Fri, 15 Sep 2017 20:43:30 +0000
Bug 1394457 - Update illustration for about:sessionrestore. ui-r=shorlander, r?dao MozReview-Commit-ID: 5952ZSBwiMs
3daddc00d9e2cc724a3a68024514f64f8f49114e: Bug 1394323 - Remove overflow css rule for 'response-panel' as it prevents scrolling in Console 'Response' tab. r=nchevobbe draft
abhinav <abhinav.koppula@gmail.com> - Sat, 16 Sep 2017 02:11:45 +0530 - rev 665672
Push 80143 by bmo:abhinav.koppula@gmail.com at Fri, 15 Sep 2017 20:42:12 +0000
Bug 1394323 - Remove overflow css rule for 'response-panel' as it prevents scrolling in Console 'Response' tab. r=nchevobbe MozReview-Commit-ID: GHbYuCfs9L
6d465c9140f057c42e5f5d5cf2cb95e1c9dc7423: Bug 1395879 - Remove espree/escope etc from the direct dependencies of eslint-plugin-mozilla since they are really peerDependencies supplied by the existing eslint peer. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Fri, 01 Sep 2017 11:27:33 +0100 - rev 665671
Push 80142 by bmo:standard8@mozilla.com at Fri, 15 Sep 2017 20:37:07 +0000
Bug 1395879 - Remove espree/escope etc from the direct dependencies of eslint-plugin-mozilla since they are really peerDependencies supplied by the existing eslint peer. r?Mossop MozReview-Commit-ID: 2FEfFaEoomU
d9e6baf7d95b8249fd918838029c720da8ee6f14: Bug 1394457 - Update illustration for about:sessionrestore. ui-r=shorlander, r?dao draft
Erica Wright <ewright@mozilla.com> - Fri, 08 Sep 2017 11:57:18 -0400 - rev 665670
Push 80141 by bmo:ewright@mozilla.com at Fri, 15 Sep 2017 20:36:25 +0000
Bug 1394457 - Update illustration for about:sessionrestore. ui-r=shorlander, r?dao MozReview-Commit-ID: 5952ZSBwiMs
829272801edae8d4d880667fe755a79ea7efee3e: Bug 1393659 - Fix inconsistent handling of max_post_bytes and max_request_bytes r?markh draft
Thom Chiovoloni <tchiovoloni@mozilla.com> - Wed, 13 Sep 2017 18:02:41 -0700 - rev 665669
Push 80140 by bmo:tchiovoloni@mozilla.com at Fri, 15 Sep 2017 20:33:31 +0000
Bug 1393659 - Fix inconsistent handling of max_post_bytes and max_request_bytes r?markh MozReview-Commit-ID: 4jwpAYNuoQj
6cd954f4d1a96fb2aedff39e047d318934f951a0: Bug 1400034 - Do a more direct translation of transforms from Gecko to WR in layers-free mode. r?ethlin,pchang draft
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 15 Sep 2017 16:30:21 -0400 - rev 665668
Push 80139 by kgupta@mozilla.com at Fri, 15 Sep 2017 20:30:43 +0000
Bug 1400034 - Do a more direct translation of transforms from Gecko to WR in layers-free mode. r?ethlin,pchang In layers-free mode the gecko display list and coordinate system is very similar to what WR is expecting. Instead of having each StackingContextHelper shift the origin of the coordinate system, we can leave it in one spot and just pass everything relative to that. The semantics of the Gecko display list already matches this; the exception is that nsDisplayTransform items are also considered reference frames, and anything inside them is relative to the nsDisplayTransform. On the WR side this is also the case, because stacking contexts with a transform are implicitly turned into reference frames. Additionally, the size of the bounds passed to the WR stacking context is never actually used, except on the root stacking context (which is not created by StackingContextHelper). Since we want a zero origin (as explained above) and the size is never used, we can just pass a zero rect to the WR stacking context from StackingContextHelper. In terms of the actual transform matrix, this patch now passes the full unmodified transform from nsDisplayTransform into WR. This transform gets applied onto the contents of the nsDisplayTransform. The contents' coordinate system is relative to the frame that generated the nsDisplayTransform. Again this maps directly to WR, where the transform on the stacking context gets applied to the contents of the stacking context; the contents' coordinates are relative to the stacking context. MozReview-Commit-ID: BQLfbKohIIm
e4ef594276e158c4daf3d66aceade29f1e59e952: Bug 1400034 - Back out changes that introduce scaling complexity to StackingContextHelper. r?ethlin,pchang draft
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 15 Sep 2017 16:30:18 -0400 - rev 665667
Push 80139 by kgupta@mozilla.com at Fri, 15 Sep 2017 20:30:43 +0000
Bug 1400034 - Back out changes that introduce scaling complexity to StackingContextHelper. r?ethlin,pchang This backs out bug 1399050, bug 1394308 (2 patches), and bug 1391499. I believe these patches sent us down a path that would make the code increasingly more complex, when in fact we can do a more "direct" translation from the gecko display list to the WR display list and make things a lot simpler and more correct. MozReview-Commit-ID: 4jJgY8Xe6xe
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip