e8ee1babd3e85c83dc2731079c5a8d74be46f47f: Bug 1373739 - Use ClientLayerManager in headless mode. r=dvander,jrmuizel
Michael Smith <michael@spinda.net> - Wed, 21 Jun 2017 08:50:02 -0700 - rev 422279
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1373739 - Use ClientLayerManager in headless mode. r=dvander,jrmuizel This fixes a series of issues uncovered by the Web Platform Tests. The most immediately noticeable symptom was that, during shutdown, PuppetWidgets on the client side attempted to delete shadow layers that were never created on the compositor side. The usage of BasicLayerManager in all other widgets due to headless mode meant that the PLayerTransactionParent was never initialized with a layer manager, and thus discarded all transaction messages it received but not delete layer messages. The effects of only using BasicLayerManager in headless mode also showed up in the web platform reftests, which ended up as blank white boxes in e10s mode as the compositor thread never received paint instructions. Switching over to using ClientLayerManager in headless mode causes these paint instructions to be relayed. In order to make ClientLayerManager work under headless mode, it was necessary to implement a HeadlessCompositorWidget and hook that up to the CompositorWidget creation function in widget/gtk. A follow-up patch will be necessary to hook up the same for the other supported widget platforms. MozReview-Commit-ID: 8vB3lrxP7iX
5cd67cab4b1124b389a05ca67d108df934eaf8ca: Bug 1373739 - Re-enable chrome-switching tests on headless mode. r=bdahl
Michael Smith <michael@spinda.net> - Tue, 27 Jun 2017 16:42:41 -0700 - rev 422278
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1373739 - Re-enable chrome-switching tests on headless mode. r=bdahl MozReview-Commit-ID: He19Xcq88vo
6ba8cca5631fafd4cbe0d13813b832ec1d4ebd80: Bug 1373739 - Simulate window activation events in headless mode. r=jrmuizel
Michael Smith <michael@spinda.net> - Wed, 21 Jun 2017 08:51:39 -0700 - rev 422277
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1373739 - Simulate window activation events in headless mode. r=jrmuizel This is necessary for focus events to propagate correctly. Otherwise, /2dcontext/drawing-paths-to-the-canvas/drawFocusIfNeeded_004.html in the Web Platform Tests fails, for example. MozReview-Commit-ID: 69GItIaQWfr
349c74ed0bd1e3d57a6182d7dbce48cc2fa294a3: Bug 1373739 - Apply thumb styles directly to their orientation variants. r=mossop
Michael Smith <michael@spinda.net> - Thu, 22 Jun 2017 17:45:50 -0700 - rev 422276
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1373739 - Apply thumb styles directly to their orientation variants. r=mossop Previously the min-height style from vertical thumbs was allowed to cascade down to horizontal thumbs. This caused broken scrollbar sizing behavior when running without a native (platform/widget toolkit) theme: horizontal scrollbars would have a non-zero height and width while vertical scrollbars would have a zero width and non-zero height. This broke one of the web platform tests in headless mode (/intersection-observer/root-margin.html). MozReview-Commit-ID: 4Y3jz77Z0UA
a179412ca028e816f367e2841f2afd91b472afe8: Bug 1373739 - Constrain widget size to screen size in headless mode. r=jrmuizel
Michael Smith <michael@spinda.net> - Thu, 22 Jun 2017 15:31:32 -0700 - rev 422275
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1373739 - Constrain widget size to screen size in headless mode. r=jrmuizel Every other widget backend ensures widget size is bounded to screen size, but this check was missing from headless. MozReview-Commit-ID: 6bKIAkdRxoO
52be5f7846f44a54451a499e47e4679a3577248c: Bug 1373739 - Disable WebGL in headless mode. r=bdahl
Michael Smith <michael@spinda.net> - Thu, 22 Jun 2017 10:13:12 -0700 - rev 422274
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1373739 - Disable WebGL in headless mode. r=bdahl MozReview-Commit-ID: LWe9hRh7zXX
f56d71bbd7eb9a9e9642c59eb7dadc5ccb6314f5: Bug 1386277: Add set methods for width and height that change nothing else, as well as the Swap method r=bas
Milan Sreckovic <milan@mozilla.com> - Thu, 03 Aug 2017 14:40:14 -0400 - rev 422273
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1386277: Add set methods for width and height that change nothing else, as well as the Swap method r=bas MozReview-Commit-ID: 5pN2aMrvAuD
a3f35ca41ccea790e1e48186a40d4c4fa026dd50: Bug 1386053 - Enable DevTools tests for Stylo Linux64. r=kmoir
J. Ryan Stinnett <jryans@gmail.com> - Mon, 31 Jul 2017 17:53:14 -0500 - rev 422272
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1386053 - Enable DevTools tests for Stylo Linux64. r=kmoir MozReview-Commit-ID: pf7Sl2I10c
7d9e2aa0650230435d5b29b5579d5f33515f8df0: Bug 1386053 - Skip remaining DevTools Stylo failures. r=manishearth
J. Ryan Stinnett <jryans@gmail.com> - Tue, 01 Aug 2017 11:52:48 -0500 - rev 422271
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1386053 - Skip remaining DevTools Stylo failures. r=manishearth MozReview-Commit-ID: TcexGI0JkG
395b4c460551181c0b191d5ee5a73aa653902bc4: Bug 1347182 - Add support for setting the background color of all toolbars using a WebExtension theme. r=jaws
Tim Nguyen <ntim.bugs@gmail.com> - Thu, 15 Jun 2017 19:20:26 +0200 - rev 422270
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1347182 - Add support for setting the background color of all toolbars using a WebExtension theme. r=jaws Original patch by :mikedeboer. MozReview-Commit-ID: IbTBCjt6oJp
faf1b9f57700234c11b89e1a18e1e3b2d58a56ec: Bug 1359157 - Support Selection.type from spec; r=smaug
Aryeh Gregor <ayg@aryeh.name> - Thu, 03 Aug 2017 17:13:24 +0300 - rev 422269
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1359157 - Support Selection.type from spec; r=smaug All other browsers already support it, more or less interoperably. MozReview-Commit-ID: 4VoOeqBoKI0
a35f3b534eb97e7a68bbe7e7effab31bf44c6adc: Bug 1355451 - Speculative connect to websites on mousedown on awesomebar item. r=mak
Evelyn Hung <jj.evelyn@gmail.com> - Thu, 03 Aug 2017 21:41:58 +0800 - rev 422268
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1355451 - Speculative connect to websites on mousedown on awesomebar item. r=mak We preconnect to an explicit URL or the url in moz-action:remotetab on the popup. MozReview-Commit-ID: 2U6nhwM6RUk
c147d7716c17ef1e4cbbf8986322742fb3c8c4c2: Bug 1386754 - Deprecate 3DES on nightly builds r=dveditz
J.C. Jones <jjones@mozilla.com> - Wed, 02 Aug 2017 11:03:39 -0700 - rev 422267
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1386754 - Deprecate 3DES on nightly builds r=dveditz 3DES usage is well below 1% [1]. A recent TLS Canary run with "security.ssl3.rsa_des_ede3_sha" disabled showed 825 of 500,000 sites being affected by deprecating 3DES [2]. This starts the deprecation by disabling the 3DES cipher suite preference in nightly builds. [1] https://mzl.la/2uNt0BP [2] https://tlscanary.mozilla.org/runs/2017-08-01-17-07-49/ MozReview-Commit-ID: C9cobeOqGLj
b3778db095815535e20637126058da3cbb40c846: Bug 1385539 - Re-add accidentally deleted documentation of mozbuild.configure.ConfigureSandbox.include_file; r=glandium
Tom Prince <mozilla@hocat.ca> - Sat, 29 Jul 2017 00:31:17 -0600 - rev 422266
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1385539 - Re-add accidentally deleted documentation of mozbuild.configure.ConfigureSandbox.include_file; r=glandium The code was deleted in Bug 1256571. MozReview-Commit-ID: JgWoxOyMQ8z
32083f24a1bb2c33050b4c972783f066432194eb: Merge inbound to central, a=merge
Wes Kocher <wkocher@mozilla.com> - Thu, 03 Aug 2017 18:06:53 -0700 - rev 422265
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Merge inbound to central, a=merge MozReview-Commit-ID: DlSLhaepjeU
33ca8807bddee0b3a17e285c8ed6d2331e6540b1: Bug 1386920 - Use a versioned dependency on GCC to build clang. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Thu, 03 Aug 2017 12:24:41 +0900 - rev 422264
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1386920 - Use a versioned dependency on GCC to build clang. r=gps The lesson learned from bug 1356926 and bug 1386588 is that the version of gcc used to build clang matters, and that we can't bind the version we use to build clang to the version we use to build Firefox.
aabe4d6900bc84a94e8b0120cfa490d2af86e5dd: Bug 1386589 - Remove the linux64 tooltool manifests that look the same as releng.manifest. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 02 Aug 2017 20:06:10 +0900 - rev 422263
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1386589 - Remove the linux64 tooltool manifests that look the same as releng.manifest. r=gps
24041731b278c34c0b76c1223cb79958cb849d18: Bug 1356926 - Enable stylo on static analysis builds. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 02 Aug 2017 19:58:59 +0900 - rev 422262
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1356926 - Enable stylo on static analysis builds. r=gps
2a497555fda7695733f438131674ab72e985b89f: Bug 1356926 - Use the same clang as normal builds for static analysis. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 02 Aug 2017 19:57:24 +0900 - rev 422261
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1356926 - Use the same clang as normal builds for static analysis. r=gps In practice, this upgrades from clang 3.8 to 3.9.
721b953ccc76287a94a1b787025127c5c0644eae: Bug 1356926 - Make all stdc++compat symbols weak. r=froydnj
Mike Hommey <mh+mozilla@glandium.org> - Thu, 03 Aug 2017 11:52:24 +0900 - rev 422260
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1356926 - Make all stdc++compat symbols weak. r=froydnj In some cases, we can end up linking some things with --static-libstdc++. The notable (only?) example of that is for the clang-plugin, and that happens because it gets some of its flags from llvm-config, which contains --static-libstdc++ because clang itself is built that way. When that happens, the combination of --static-libstdc++ and stdc++compat breaks the build because they have conflicting symbols, which is very much by design. There are two ways out of this: - avoiding either -static-libstdc++ or stdc++compat - work around the symbol conflicts The former is not totally reliable ; we'd have to accurately determine if we're in a potentially conflicting case, and remove one of the two in that case, and while we can do that for the cases we explicitly know about, that's not future-proof, and might fail just as much in the future. So we go with the latter. The way we do this is by defining all the std++compat symbols weak, such that at link time, they're overridden by any symbol with the same name. When building with -static-libstdc++, libstdc++.a provides those symbols so the linker eliminates the weak ones. When not building with -static-libstdc++, the linker keeps the symbols from stdc++compat. That last assertion is validated by the long-standing CHECK_STDCXX test that we run when linking shared libraries and programs. That still leaves the symbols weak in the final shared libraries/programs, which is a change from the current setup, but shouldn't cause problems because when using versions of libstdc++.so that do provide those symbols, it's fine to use the libstdc++.so version anyways.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip