aa02fa00af6f2d7495a6c9193ce812ce622b0393: Bug 1410906 - Store ThemeGeometry for display item instead of frame r=mattwoodrow
Miko Mynttinen <mikokm@gmail.com> - Mon, 23 Oct 2017 18:07:36 +0200 - rev 387814
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1410906 - Store ThemeGeometry for display item instead of frame r=mattwoodrow MozReview-Commit-ID: 6x7GRRTEVja
09f25b91132eb1f2391f2dabe1569cbd31a7c655: Bug 1395151 - Don't apply ancestors' opacity if the opacity item has an async opacity animation. r=birtles,mattwoodrow
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Mon, 23 Oct 2017 19:26:40 +0900 - rev 387813
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1395151 - Don't apply ancestors' opacity if the opacity item has an async opacity animation. r=birtles,mattwoodrow MozReview-Commit-ID: KsxukpGrH6P
b6101f641ea7d7967126be028170cdb8494d5e84: bug 1410043 remove over-zealous graph-thread assert in SetCurrentDriver() r=pehrsons
Karl Tomlinson <karlt+@karlt.net> - Fri, 20 Oct 2017 17:59:19 +1300 - rev 387812
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
bug 1410043 remove over-zealous graph-thread assert in SetCurrentDriver() r=pehrsons The reverts to accepting ownership of the monitor regardless of the thread, as accepted prior to https://hg.mozilla.org/mozilla-central/rev/e3f39de40209#l1.25 As indicated in the SetCurrentDriver() documentation, it can be called on the main thread during Revive() before another graph thread is started. At that point mLifecycleState = LIFECYCLE_RUNNING, and so it is not easy to adjust AssertOnGraphThreadOrNotRunning() to accept this situation without making it much more liberal. An alternative would be to change the Revive() methods to set mDriver directly, but that would differ from the usual driver-switching pattern. MozReview-Commit-ID: 9O5qakPVML9
10027a261e8a8427fb6eae3fd60914628a519661: Bug 1407735 - Make the JS loader XPCOM component use a singleton. r=kmag
Andrew McCreight <continuation@gmail.com> - Mon, 23 Oct 2017 13:53:58 -0700 - rev 387811
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1407735 - Make the JS loader XPCOM component use a singleton. r=kmag mozJSComponentLoader is created using XPCOM. However, you can only call it once or it'll crash. This patch fixes that by using a singleton macro. MozReview-Commit-ID: Bq2k7nv9dKA
9e434f5e600da187b745b4baaa6822a728a4c0be: Bug 1379332 followup: Skip this bug's crashtests on Android to avoid triggering "boolean preference...not known or wrong type" error there. (test-only, no review)
Daniel Holbert <dholbert@cs.stanford.edu> - Mon, 23 Oct 2017 15:28:00 -0400 - rev 387810
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1379332 followup: Skip this bug's crashtests on Android to avoid triggering "boolean preference...not known or wrong type" error there. (test-only, no review) MozReview-Commit-ID: 6G8euT0w0A9
6a9ca63ae2b5921b0e9f0f31ce80fe0adffa04e7: Backed out changeset 09f2bfedb4db for landing with the wrong bug number in the commit message.
Ryan VanderMeulen <ryanvm@gmail.com> - Mon, 23 Oct 2017 18:35:21 -0400 - rev 387809
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Backed out changeset 09f2bfedb4db for landing with the wrong bug number in the commit message.
76300bd1f7c18286fd6e280df454e97755ff6524: Bug 1400238 - Notify TabParent when the GTK client offset changes. r=karlt
Botond Ballo <botond@mozilla.com> - Wed, 18 Oct 2017 13:29:47 -0400 - rev 387808
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1400238 - Notify TabParent when the GTK client offset changes. r=karlt MozReview-Commit-ID: 1TacAhl6c2M
09f2bfedb4db08356b3a275972bacac1a1ce500d: Bug 1350948 followup: Skip this bug's crashtests on Android to avoid triggering "boolean preference...not known or wrong type" error there. (test-only, no review)
Daniel Holbert <dholbert@cs.stanford.edu> - Mon, 23 Oct 2017 15:28:00 -0400 - rev 387807
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1350948 followup: Skip this bug's crashtests on Android to avoid triggering "boolean preference...not known or wrong type" error there. (test-only, no review) MozReview-Commit-ID: 6G8euT0w0A9
ca99e68b3b36a725b1dc545357cd25e82cdf0caf: Bug 607818 Fix bootstrap reasons during addon upgrade/downgrade operations r=kmag
Andrew Swan <aswan@mozilla.com> - Sat, 21 Oct 2017 20:07:09 -0700 - rev 387806
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 607818 Fix bootstrap reasons during addon upgrade/downgrade operations r=kmag When the same addon is installed in multiple locations and the copy in the highest priority location is removed, we reveal the next-highest priority copy. Since we're just changing addon versions, this sequence should look like an upgrade or downgrade. This patch fixes the reason parameter passed to both instance's bootstrap methods to reflect that. MozReview-Commit-ID: DfQadQFufZE
2bb423b449371ceaa7496347763b6fac6e0dd649: Bug 1410904 - Convert WeakFrame to nsIFrame* earlier to avoid copying WeakFrames r=mattwoodrow
Miko Mynttinen <mikokm@gmail.com> - Mon, 23 Oct 2017 18:19:39 +0200 - rev 387805
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1410904 - Convert WeakFrame to nsIFrame* earlier to avoid copying WeakFrames r=mattwoodrow MozReview-Commit-ID: KVzOtVATpNa
e1bcd28b3323bb1932b7c0dc895a653057a69ae9: Bug 1410876 - Use AUTO_PROFILER_TRACING instead of AutoProfilerTracing r=mattwoodrow
Miko Mynttinen <mikokm@gmail.com> - Mon, 23 Oct 2017 15:07:53 +0200 - rev 387804
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1410876 - Use AUTO_PROFILER_TRACING instead of AutoProfilerTracing r=mattwoodrow MozReview-Commit-ID: 55A1Aih6MzA
d2edccc49998aa5ddc9bb242f7115b5ba3367f28: merge mozilla-central to autoland. r=merge a=merge
Sebastian Hengst <archaeopteryx@coole-files.de> - Mon, 23 Oct 2017 23:52:54 +0200 - rev 387803
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
merge mozilla-central to autoland. r=merge a=merge
7361a04cfd7c3237738d44122550ab755a3346fc: Bug 1410944 - Support uninstalling a duplicated registry entry we might have erroneously created. r=agashlin
Matt Howell <mhowell@mozilla.com> - Mon, 23 Oct 2017 11:04:59 -0700 - rev 387802
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1410944 - Support uninstalling a duplicated registry entry we might have erroneously created. r=agashlin MozReview-Commit-ID: 3WR2NfAYFgl
26444ee0baf18f08fded67982ee28b232c44e0c1: Bug 1410769: Use SHA-1 signing when MAR_OLD_FORMAT is set; r=nalexander,rstrong
Tom Prince <mozilla@hocat.ca> - Sun, 22 Oct 2017 21:46:41 -0600 - rev 387801
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1410769: Use SHA-1 signing when MAR_OLD_FORMAT is set; r=nalexander,rstrong MozReview-Commit-ID: DFjcozLqskI
e91ca49ccf6c6f5069f217cf971b34df4b4edbe0: Bug 1379332: When computing abspos CB content-box size, don't bother subtracting borderpadding if CB is a 0-sized child of a XUL-collapsed frame. r=mats
Daniel Holbert <dholbert@cs.stanford.edu> - Fri, 20 Oct 2017 16:40:43 -0700 - rev 387800
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1379332: When computing abspos CB content-box size, don't bother subtracting borderpadding if CB is a 0-sized child of a XUL-collapsed frame. r=mats If border & padding were ignored for sizing the containing block (which can happen, if the containing block is a chlid of a XUL-collapsed frame), then we don't need to subtract border & padding when computing the frame's content-box size for its abspos descendants. MozReview-Commit-ID: JGnzShl8m67
b46909f2b66883d73baf628316739cb9a0e1de93: Bug 1247149 - mozscreenshots: Support restricting configurations in sets. r=jaws
Rand Mustafa <rndmustafa@gmail.com> - Tue, 09 Feb 2016 19:12:40 -0800 - rev 387799
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1247149 - mozscreenshots: Support restricting configurations in sets. r=jaws The initial commit was authored by Kit Cambridge. His commit enabled the user to specify a single configuration in a set e.g. Toolbars[onlyNavBar],Tabs. The next set of commits allowed multiple configurations to be specified and also checked the validity of the configurations. Various bugs were squashed along the way. MozReview-Commit-ID: LTT7auJfcHa
51fded9c47aa99770e9c2b5a85e82bd988b12e57: Bug 1403682 - Add _findBoundingBox function and tests for mozscreenshots cropping; r=jaws
Mike Williams <will2616@msu.edu> - Sat, 14 Oct 2017 11:13:32 -0400 - rev 387798
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1403682 - Add _findBoundingBox function and tests for mozscreenshots cropping; r=jaws MozReview-Commit-ID: 7kvVsF3Wq3z
b43cc917edadafe3c06888ba02d464a12b2d502b: Bug 1410624: Add some declarations and bindings so the build isn't busted when servo-vcs-sync goes back alive. r=me,heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 23 Oct 2017 22:36:59 +0200 - rev 387797
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1410624: Add some declarations and bindings so the build isn't busted when servo-vcs-sync goes back alive. r=me,heycam https://github.com/servo/servo/pull/18988 has merged a while ago in servo, but since the sync service is down, I haven't been able to land the relevant patches today. This at least ensures that the build isn't busted when servo-vcs-sync goes back up. MozReview-Commit-ID: 9ohgwcnMc5T
ebe89bb81bc82615518e6094fa40640816bb0569: Bug 1410451 - Do not merge en-US file for missing .ftl file in JarMaker. r=mshal
Zibi Braniecki <zbraniecki@mozilla.com> - Fri, 20 Oct 2017 09:12:29 -0700 - rev 387796
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1410451 - Do not merge en-US file for missing .ftl file in JarMaker. r=mshal MozReview-Commit-ID: DxDAKGC7NKm
057166cb35fe9a0df57adf0778539d64f2e550d2: Bug 1359908 Add FORTIFY_SOURCE to gcc and clang builds by default r=froydnj
Tom Ritter <tom@mozilla.com> - Thu, 19 Oct 2017 01:43:07 -0500 - rev 387795
Push 96497 by archaeopteryx@coole-files.de at Tue, 24 Oct 2017 09:57:53 +0000
Bug 1359908 Add FORTIFY_SOURCE to gcc and clang builds by default r=froydnj This adds a section in both old-configure.in's for hardening flags. In old-configure.in we add $HARDENING_CFLAGS (which are turned on by --enable-hardening) and are defined in toolchain.configure (and which does compiler detection there.) We then add non-optional hardening flags, performing compiler detection here. In js/src/old-configure.in we follow the same pattern, but omit $HARDENING_CFLAGS because we don't apply the current lone flag to js (doing so is Bug 1359905). MozReview-Commit-ID: EFE0Pc7yZHa
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip