641fa04790771eff942517d200348a72501c09e7: Back out changesets from bug 1342567.
Timothy Nikkel <tnikkel@gmail.com> - Wed, 17 May 2017 16:17:23 -0500 - rev 579871
Push 59390 by bmo:mh+mozilla@glandium.org at Wed, 17 May 2017 21:49:26 +0000
Back out changesets from bug 1342567. Backed out changeset 06d6f928ed64 * * * Backed out changeset f577512b1a29 * * * Backed out changeset 289645ac65c1 * * * Backed out changeset 600f9d60d76f * * * Backed out changeset 445330fd1211
2aa6d03565faddb0072e125e8cd2d1583ef05aac: Bug 1347750 - Generate old-style DWARF info for fuzzing builds, r=glandium
Steve Fink <sfink@mozilla.com> - Wed, 10 May 2017 12:12:06 -0700 - rev 579870
Push 59390 by bmo:mh+mozilla@glandium.org at Wed, 17 May 2017 21:49:26 +0000
Bug 1347750 - Generate old-style DWARF info for fuzzing builds, r=glandium
7ac6454c755a97d6a2dcdd190d99454dd7920f3d: Bug 1339989 - Add --no-build option to build-gcc.sh, r=glandium
Steve Fink <sfink@mozilla.com> - Mon, 17 Apr 2017 14:51:17 -0700 - rev 579869
Push 59390 by bmo:mh+mozilla@glandium.org at Wed, 17 May 2017 21:49:26 +0000
Bug 1339989 - Add --no-build option to build-gcc.sh, r=glandium
f4a2a967c85e39314d0ca1cfd6a76feed2c6527d: Bug 1365660: Part 5c - Enable compositing for popups with remote content on OS-X. r?mstange draft
Kris Maglione <maglione.k@gmail.com> - Wed, 17 May 2017 14:46:11 -0700 - rev 579868
Push 59389 by maglione.k@gmail.com at Wed, 17 May 2017 21:48:42 +0000
Bug 1365660: Part 5c - Enable compositing for popups with remote content on OS-X. r?mstange MozReview-Commit-ID: 90JJVJ2eR9C
61b0bbc674f69866e6113df0638e136be8013b88: Bug 1365660: Part 5b - Enable compositing for popups with remote content on Windows. r?bas.schouten draft
Kris Maglione <maglione.k@gmail.com> - Tue, 16 May 2017 14:30:51 -0700 - rev 579867
Push 59389 by maglione.k@gmail.com at Wed, 17 May 2017 21:48:42 +0000
Bug 1365660: Part 5b - Enable compositing for popups with remote content on Windows. r?bas.schouten MozReview-Commit-ID: GzpCBUnVkdY
f1739e2666034620192f80ecb3a05f3a80a465d5: Bug 1365660: Part 5a - Enable compositing for popups with remote content on Linux. r?marco draft
Kris Maglione <maglione.k@gmail.com> - Tue, 16 May 2017 14:30:24 -0700 - rev 579866
Push 59389 by maglione.k@gmail.com at Wed, 17 May 2017 21:48:42 +0000
Bug 1365660: Part 5a - Enable compositing for popups with remote content on Linux. r?marco MozReview-Commit-ID: C3oykBO7oHJ
77e773de3d206366d5b2bbd6a6aacfe90dd3216f: Bug 1365660: Part 4 - Only enable APZ for popups which contain remote content. r?kats draft
Kris Maglione <maglione.k@gmail.com> - Tue, 16 May 2017 14:28:20 -0700 - rev 579865
Push 59389 by maglione.k@gmail.com at Wed, 17 May 2017 21:48:42 +0000
Bug 1365660: Part 4 - Only enable APZ for popups which contain remote content. r?kats We only ever need to enable APZ for popups which contain remote content. In theory, enabling it for other popups shouldn't hurt, but having it enabled adds overhead that we'd rather avoid, and causes painting issues under some circumstances. Ideally, the painting issues should be fixed, but disabling APZ is a good short term workaround, and we should try to avoid the unnecessary overhead either way. MozReview-Commit-ID: AOivnTQBWQh
5d302681d2a65eac15bdb7d1cacd9d7c92f8dde3: Bug 1365660: Part 3 - Disable transparency (where necessary) and drop shadows for popups which contain remote content. r?mstange,bas.schouten draft
Kris Maglione <maglione.k@gmail.com> - Tue, 16 May 2017 14:29:35 -0700 - rev 579864
Push 59389 by maglione.k@gmail.com at Wed, 17 May 2017 21:48:42 +0000
Bug 1365660: Part 3 - Disable transparency (where necessary) and drop shadows for popups which contain remote content. r?mstange,bas.schouten Drop shadows are currently not handled correctly for animated, composited popups on Windows and OS-X. The shadows are rendered, but are not correctly updated to match the final popup size. Ideally, we should support drop shadows for these popups correctly, but in the interim, disabling them gives better results. Transparency is not handled correctly for composited popups on any platform, but works with varying degrees of success on some platforms, for some popups. Oddly, out of the three main desktop platforms, Linux seems to handle it the best, so long as we render the popup as opaque, and let the platform compositor handle the transparency. MozReview-Commit-ID: E8NQlToUQq3
1ab6b328ce4190f40934720c9c4c1fd94107d217: Bug 817374 - Fix inconsistency of the setOverLink parameter. r=mossop draft
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Mon, 21 Nov 2016 21:39:15 +0900 - rev 579863
Push 59388 by VYV03354@nifty.ne.jp at Wed, 17 May 2017 21:47:48 +0000
Bug 817374 - Fix inconsistency of the setOverLink parameter. r=mossop MozReview-Commit-ID: 6rLOm1T2sOd
51f530ea5712af3ef1e5395239e2864342037f57: Bug 1358907 Avoid reading XPI database at startup draft
Andrew Swan <aswan@mozilla.com> - Tue, 16 May 2017 22:26:01 -0700 - rev 579862
Push 59387 by aswan@mozilla.com at Wed, 17 May 2017 21:24:44 +0000
Bug 1358907 Avoid reading XPI database at startup Experiments and TelemetryEnvironment were both calling AddonManager.getAddonsByTypes() during startup which caused the XPI database to be loaded. We can get some basic information about addons without the XPI database so now we defer that work until after startup. MozReview-Commit-ID: Fj6z5eYgYYC
69af6b119c038f7c79dcbfa97f7e3b22d8997dac: Bug 1359417 WebExtensions ProxyAPI uses HTTPS proxy instead of HTTP proxy and Bug 1362798 WebExtensions ProxyAPI should support return strings HTTP and SOCKS4 draft
Eric Jung <eric@ericjung.net> - Fri, 12 May 2017 12:18:28 -0600 - rev 579861
Push 59386 by bmo:eric@ericjung.net at Wed, 17 May 2017 21:21:43 +0000
Bug 1359417 WebExtensions ProxyAPI uses HTTPS proxy instead of HTTP proxy and Bug 1362798 WebExtensions ProxyAPI should support return strings HTTP and SOCKS4 MozReview-Commit-ID: GSxv0s8RPbo
483c4311dfd6bcbf45754ec2478b19e410a28d46: Bug 1365637 place WE sidebars into the photon sidebar dropdwon, r?mattw,aswan draft
Shane Caraveo <scaraveo@mozilla.com> - Wed, 17 May 2017 14:17:48 -0700 - rev 579860
Push 59385 by mixedpuppy@gmail.com at Wed, 17 May 2017 21:18:29 +0000
Bug 1365637 place WE sidebars into the photon sidebar dropdwon, r?mattw,aswan MozReview-Commit-ID: 91ksKoryZpr
5c210f6fd75fa5b8bf240f34040595956abee5ca: Bug 1359733 -- (pt. 5) Pull out indicator.js badges draft
Doug Thayer <dothayer@mozilla.com> - Mon, 15 May 2017 11:57:58 -0700 - rev 579859
Push 59384 by bmo:dothayer@mozilla.com at Wed, 17 May 2017 21:09:44 +0000
Bug 1359733 -- (pt. 5) Pull out indicator.js badges See also pt. 4. We are moving app menu notification state into a jsm since it is not specific to one window and this simplifies work for the new app update UI. MozReview-Commit-ID: InEp5b0y2n0
ca6686804a88fdc7a8b9831f21d73fbf44fb3b9d: Bug 1359733 - (pt. 4) Pull out browser-sync.js badges draft
Doug Thayer <dothayer@mozilla.com> - Wed, 17 May 2017 14:05:44 -0700 - rev 579858
Push 59384 by bmo:dothayer@mozilla.com at Wed, 17 May 2017 21:09:44 +0000
Bug 1359733 - (pt. 4) Pull out browser-sync.js badges See also commit message for pt. 4. We're moving app menu notification state into a jsm. MozReview-Commit-ID: 3RehYcHyfLu
38982da57a18a8311b5062b96a7f71ee4ded5c52: Bug 1359733 - (pt. 3) Pull out browser-addons.js badges draft
Doug Thayer <dothayer@mozilla.com> - Mon, 15 May 2017 10:38:33 -0700 - rev 579857
Push 59384 by bmo:dothayer@mozilla.com at Wed, 17 May 2017 21:09:44 +0000
Bug 1359733 - (pt. 3) Pull out browser-addons.js badges We are moving app menu doorhangers and badges out from window- specific code into a jsm, in order to simplify the work that the new app udpate UI has to do. Since browser-addons.js also consumes the badge system, this ensures that it also uses the jsm store. MozReview-Commit-ID: Fb5Fsja0RcA
5fdddc1045bd28aa63caf06114c8172d7acba0dd: Bug 1359733 - (pt. 2) Refactor gMenuButtonUpdateBadge draft
Doug Thayer <dothayer@mozilla.com> - Wed, 17 May 2017 14:06:56 -0700 - rev 579856
Push 59384 by bmo:dothayer@mozilla.com at Wed, 17 May 2017 21:09:44 +0000
Bug 1359733 - (pt. 2) Refactor gMenuButtonUpdateBadge Since we now have a store of notifications that is global across all windows, it no longer makes sense to consume the API from within browser.js. This patch moves the browser.js logic out into a jsm file that is wired up through nsBrowserGlue, such that it will be lazily instantiated on the first update event it would receive[1]. I was uncertain where this code should go. browser/components seemed to be the only place that made sense, but suggestions would be appreciated. There will be another patch moving the tests from browser/base/content into browser/components, but for now I wanted to make sure the diff was clean. [1]: There is a change to nsBrowserGlue to use "global[module]" instead of this[module]. This mirrors the code for all the other types of notifications, and I suspect it was just a latent bug, since the original diff that includes this line makes no use of it. MozReview-Commit-ID: 8EQdM9BOpgl
5da9d9ac8acf90f2446d1068589f1a4d314c0695: Bug 1364047 - Pull WebConsoleUtils.l10n into its own module;r=Honza draft
Brian Grinstead <bgrinstead@mozilla.com> - Wed, 17 May 2017 14:07:03 -0700 - rev 579855
Push 59383 by bgrinstead@mozilla.com at Wed, 17 May 2017 21:07:13 +0000
Bug 1364047 - Pull WebConsoleUtils.l10n into its own module;r=Honza MozReview-Commit-ID: LI5Hrs33CVS
e1fb5b641b3d794eb659927b8a68f67d8bef31c1: Bug 1362213 - WIP, don't commit yet draft
Kearwood Gilbert <kearwood@kearwood.com> - Mon, 08 May 2017 16:01:36 -0700 - rev 579854
Push 59382 by bmo:kgilbert@mozilla.com at Wed, 17 May 2017 21:02:58 +0000
Bug 1362213 - WIP, don't commit yet MozReview-Commit-ID: BMEIPyYeEbq
d9fe525f493d234d2684f09802fe7cda698b9b59: Bug 1365509: Don't trigger a sync load of the add-ons DB at startup when a built-in LWT is enabled. r?rhelmer draft
Kris Maglione <maglione.k@gmail.com> - Wed, 17 May 2017 13:51:42 -0700 - rev 579853
Push 59381 by maglione.k@gmail.com at Wed, 17 May 2017 20:53:16 +0000
Bug 1365509: Don't trigger a sync load of the add-ons DB at startup when a built-in LWT is enabled. r?rhelmer MozReview-Commit-ID: AG0dXSnBwZ3
f0ce0e47812e64a8bef91115dcfe99c62ba46923: Bug 1365509: Special case handling of enabled state for XUL themes. r?rhelmer draft
Kris Maglione <maglione.k@gmail.com> - Wed, 17 May 2017 13:48:47 -0700 - rev 579852
Push 59381 by maglione.k@gmail.com at Wed, 17 May 2017 20:53:16 +0000
Bug 1365509: Special case handling of enabled state for XUL themes. r?rhelmer Legacy XUL themes are treated specially for chrome registration when a lightweight theme is enabled. In those cases, all XUL themes are marked as disabled for the purposes of UI, but chrome for the default theme still needs to be loaded. So we need to treate the `selectedTheme` as enabled for chrome registration purposes regardless of its database disabled state. MozReview-Commit-ID: EZLckFhftqt
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip