115ca10fde0e8b7cfb0d34087a030959e0e5b18b: Bug 1446064 - Clean up webconsole-connection-proxy.js. r=nchevobbe
J. Ryan Stinnett <jryans@gmail.com> - Thu, 15 Mar 2018 13:04:14 -0500 - rev 464486
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1446064 - Clean up webconsole-connection-proxy.js. r=nchevobbe MozReview-Commit-ID: LWRuJQJgkrm
647154f3033288e3cc3552f86d92eb1ad5f8f742: Bug 1415733 - Migrate the "Search" section of Preferences to the new Localization API. r=flod,Gijs
Zibi Braniecki <zbraniecki@mozilla.com> - Mon, 12 Mar 2018 17:17:13 -0700 - rev 464485
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1415733 - Migrate the "Search" section of Preferences to the new Localization API. r=flod,Gijs MozReview-Commit-ID: ltXNOkdnOV
72a41cf593c7416619b3da744603c65108bf173f: Backed out 8 changesets (bug 1445662) for bustage at build/src/gfx/layers/apz/util/ChromeProcessController.cp on a CLOSED TREE
Coroiu Cristina <ccoroiu@mozilla.com> - Thu, 15 Mar 2018 20:37:10 +0200 - rev 464484
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Backed out 8 changesets (bug 1445662) for bustage at build/src/gfx/layers/apz/util/ChromeProcessController.cp on a CLOSED TREE Backed out changeset d514b05d1f6a (bug 1445662) Backed out changeset 13f4f51d7bd1 (bug 1445662) Backed out changeset 20c79dee1905 (bug 1445662) Backed out changeset ca1e29c9b439 (bug 1445662) Backed out changeset 8fadda7d555e (bug 1445662) Backed out changeset b5f2ceda75bd (bug 1445662) Backed out changeset 41d8b7a6b339 (bug 1445662) Backed out changeset 121cd3a0490f (bug 1445662)
32f45689f03377c8345812106cfcf1b82b322140: Bug 1445084 - Migrate search results pane of Preferences to Fluent. r=flod,Gijs
Zibi Braniecki <zbraniecki@mozilla.com> - Mon, 12 Mar 2018 16:27:32 -0700 - rev 464483
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445084 - Migrate search results pane of Preferences to Fluent. r=flod,Gijs MozReview-Commit-ID: BNeocrSY5Fa
880736d97de3f973f545abdbcc993cd4288f217c: Bug 1358815 - update pdfjs for async-created findbar, r=bdahl
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 13 Mar 2018 11:52:56 +0000 - rev 464482
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1358815 - update pdfjs for async-created findbar, r=bdahl MozReview-Commit-ID: Byr5B4yAzfx
a2a0a0990e1af140deffeb8aa66dd47f4c3aae10: Bug 1358815 - remove sync reflow from find bar initialization, r=jaws
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Mon, 12 Mar 2018 14:01:44 +0000 - rev 464481
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1358815 - remove sync reflow from find bar initialization, r=jaws This removes the sync reflow from almost all cases. The only case where we keep it is when a keypress caught in content triggers a sync message to the parent process. We should clean this up in bug 1371523. I've tried to fix the tests, but a lot of them seem to be disabled anyway... MozReview-Commit-ID: 9k36p7q8MKy
2cab87e3a891fcdf4ef78b1dc01a6b7b5e69c853: Bug 1444521 - Preferences UI save to cloud downloads event listener r=jaws
Punam <pdahiya@mozilla.com> - Tue, 13 Mar 2018 17:54:18 -0700 - rev 464480
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1444521 - Preferences UI save to cloud downloads event listener r=jaws MozReview-Commit-ID: LbKr1rpXn4q
d514b05d1f6a60aae21ba4a22c6b7af43fc06d76: Bug 1445662 - Update RemoteContentController to allow the GPU process controller thread to be different from the compositor thread. r=rhunt
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 14 Mar 2018 16:57:52 -0400 - rev 464479
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445662 - Update RemoteContentController to allow the GPU process controller thread to be different from the compositor thread. r=rhunt A couple of RemoteContentController methods get called on the controller thread in the GPU process. This is the same as the compositor thread so we could just do compositor-thread stuff here, but we will want to support the controller thread being the main thread instead of the compositor thread. So we detect those cases and bounce the message accordingly. MozReview-Commit-ID: 6kLqdl6jgO0
13f4f51d7bd1e999af621eeef4587455aed79e05: Bug 1445662 - Annotate remaining PAPZCTreeManager-invoked methods with threading constraints. r=rhunt
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 14 Mar 2018 16:57:52 -0400 - rev 464478
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445662 - Annotate remaining PAPZCTreeManager-invoked methods with threading constraints. r=rhunt These methods are already guaranteed to be called on the controller thread. MozReview-Commit-ID: 4pfUZe6cI8e
20c79dee1905275492f557cee4a51aa6d92fbf24: Bug 1445662 - Ensure ZoomToRect runs on the controller thread. r=rhunt
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 14 Mar 2018 16:57:52 -0400 - rev 464477
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445662 - Ensure ZoomToRect runs on the controller thread. r=rhunt Currently the ZoomToRect function is only ever called on Android, on the UI process main thread, which is neither the controller nor the sampler thread. Instead of allowing "random" threads to run inside APZ, we ensure that callers run it on the controller thread. MozReview-Commit-ID: 64LkHaFLIOl
ca1e29c9b4394a47077e2ff5a60ad5307b9ee43b: Bug 1445662 - Ensure UpdateZoomConstraints runs on the sampler thread. r=rhunt
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 14 Mar 2018 16:57:42 -0400 - rev 464476
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445662 - Ensure UpdateZoomConstraints runs on the sampler thread. r=rhunt Without this patch, UpdateZoomConstraints can get called on: a) the compositor/sampler thread (over PAPZCTreeManager) b) the controller thread which is also the UI process main thread (on desktop platforms without a GPU process) c) the UI process main thread when it's *not* the controller thread (on Android). Instead of having to reason about all these scenarios separately, we can try to unify them a little bit by ensuring the function contents always run on the sampler thread, which is the thread that seems to make the most sense for it. MozReview-Commit-ID: 8V4WTNtST3d
8fadda7d555ed02b876598b16b2e683211858ba8: Bug 1445662 - Assert that IAPZCTreeManager's helper methods are always on the controller thread. r=rhunt
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 14 Mar 2018 16:57:41 -0400 - rev 464475
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445662 - Assert that IAPZCTreeManager's helper methods are always on the controller thread. r=rhunt These two functions (UpdateWheelTransaction and ProcessUnhandledEvent) are only ever called on the concrete APZCTreeManager when the APZ code is living in the GPU process. This is because the calls are made by the IAPZCTreeManager implementation which lives in the UI process, and remoted over PAPZCTreeManager. So the assertion is safe, and will help us guard against inadvertent breakage when we try making a different thread the controller thread in the GPU process. In addition, the WillHandleInput function can be called in the GPU process on the compositor thread, but we will allow it to be called on the main thread as well. In that case we need to ensure we don't try running EventStateManager pref-reading code in the GPU process, and instead preserve the current behaviour of just returning true. MozReview-Commit-ID: JFBX3NSXywn
b5f2ceda75bd9ea493d660d7d568f518f00b27fc: Bug 1445662 - Remove ProcessTouchVelocity from PAPZCTreeManager.ipdl. r=rhunt
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 14 Mar 2018 16:57:41 -0400 - rev 464474
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445662 - Remove ProcessTouchVelocity from PAPZCTreeManager.ipdl. r=rhunt This function is never actually called over IPDL. It is called directly on the concrete APZCTreeManager instance by the AndroidDynamicToolbarAnimator code, both of which live in the compositor. So we don't need to expose this method on IAPZCTreeManager or over PAPZCTreeManager. MozReview-Commit-ID: 6fEkJpDDvhl
41d8b7a6b339659290c1807e4fd94d7e2f0bda45: Bug 1445662 - Make the DPI non-static and bound to the controller thread. r=rhunt
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 14 Mar 2018 16:57:41 -0400 - rev 464473
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445662 - Make the DPI non-static and bound to the controller thread. r=rhunt Since we can have multiple browser windows on multiple different displays with different DPIs, it doesn't make sense to have a single static DPI value shared across all APZCTreeManagers. Instead, each APZCTM should store its own DPI value for the display the window is on. Since the DPI is only ever read from the controller thread, we can make it bound to that thread, and update the setter code to also set it on that thread. As with the previous patch, the change in APZCTreeManagerParent is a no-op but allows making some other thread in the GPU process the controller thread. And the change in nsBaseWidget is a no-op everywhere except Android. MozReview-Commit-ID: CB23MxGISeL
121cd3a0490f2493f669b6c622e559ce683050ef: Bug 1445662 - Ensure the keyboard map access is threadsafe. r=rhunt
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 14 Mar 2018 16:57:41 -0400 - rev 464472
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445662 - Ensure the keyboard map access is threadsafe. r=rhunt - The change in APZCTreeManagerParent is functionally a no-op because it only ever runs in the GPU process on the controller thread. But it allows moving the controller thread to some other thread. - The change in nsBaseWidget is a no-op for desktop platforms, because in the UI process the main thread is the controller thread. But on Android it moves the call from the main thread to the Java UI thread. MozReview-Commit-ID: LVVZLFxSuyj
97d4f8fe732d6b7bb2b3031ba3684159ce0810f7: Merge mozilla-central to autoland. a=merge CLOSED TREE
Noemi Erli <nerli@mozilla.com> - Thu, 15 Mar 2018 19:44:05 +0200 - rev 464471
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Merge mozilla-central to autoland. a=merge CLOSED TREE
aebdf3532d2f4bcd32a03e87ac8af9433db8b92c: Bug 1445958 - fixed a method name name in a comment; r=jrmuizel
Alex Gaynor <agaynor@mozilla.com> - Thu, 15 Mar 2018 10:31:28 -0400 - rev 464470
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1445958 - fixed a method name name in a comment; r=jrmuizel MozReview-Commit-ID: DHvy0cufcXt
8cad90854096397d603810b396282e399bea4709: servo: Merge #20260 - Run automated test for memory report charter (from servo:jdm-patch-11); r=asajeffrey
Josh Matthews <josh@joshmatthews.net> - Thu, 15 Mar 2018 11:07:40 -0400 - rev 464469
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
servo: Merge #20260 - Run automated test for memory report charter (from servo:jdm-patch-11); r=asajeffrey No point in having tests if they don't get run. Source-Repo: https://github.com/servo/servo Source-Revision: 1c7424d9206605e8a3dbf851b8d6900dfa4906b9
4e4b09a24ae786a8fffe7f3ba954b87ece7cf938: Bug 1442302 - Remove placesOverlay.xul. r=Gijs,mak,standard8
Brendan Dahl <brendan.dahl@gmail.com> - Mon, 12 Mar 2018 10:43:35 -0700 - rev 464468
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1442302 - Remove placesOverlay.xul. r=Gijs,mak,standard8 The overlay was responsible for script loading and defining three elements (bhTooltip, placesCommands, placesContext). In the majority of places where the overlay was included only part of it was used. To remove the overlay, the elements were each split into include files and moved into where they were used. For the scripts, a JS file was added that defines all the lazy modules and then this script, globalOverlay.js and utilityOverlay.js were inlined to everywhere that would have included them from the overlay. MozReview-Commit-ID: 8T5D46oYWLn
fbdaeb6f64ca0f9b81bd72d53f8cba414047a334: Bug 1406206 - Remove extraneous else block from cycle collection macros; r=froydnj
Kyle Machulis <kyle@nonpolynomial.com> - Wed, 14 Mar 2018 15:36:59 -0700 - rev 464467
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1406206 - Remove extraneous else block from cycle collection macros; r=froydnj clang-tidy is complaining about an extra else in NS_INTERFACE_MAP_ENTRIES_CYCLE_COLLECTION. Not hurting anything, but could be cleaned up anyways. MozReview-Commit-ID: 36Lkdhs3fyN
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip