d78701ac0ea19f849ca73dac988484a8da9d3635: bug 1457058 remove unused GraphDriver::RemoveCallback() r=padenot
Karl Tomlinson <karlt+@karlt.net> - Thu, 26 Apr 2018 17:50:59 +1200 - rev 415953
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
bug 1457058 remove unused GraphDriver::RemoveCallback() r=padenot MozReview-Commit-ID: 3ZWfWEJ7bko
63fca25d8f74d8d59b551b3d8e99826497f878f9: bug 1457060 dereference MixerCallback and receiver on separate lines r=padenot
Karl Tomlinson <karlt+@karlt.net> - Thu, 26 Apr 2018 18:30:31 +1200 - rev 415952
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
bug 1457060 dereference MixerCallback and receiver on separate lines r=padenot MozReview-Commit-ID: JNltGvA6tMv
0ae9810db35257d6f3b1159fdbde04917871d231: Bug 1457287 - Follow-up to fix browser_address_edit.js. r=jaws on a CLOSED TREE
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Thu, 26 Apr 2018 18:08:34 -0700 - rev 415951
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1457287 - Follow-up to fix browser_address_edit.js. r=jaws on a CLOSED TREE MozReview-Commit-ID: 1StIu61pvwD
8c7c5f3460062a19cc709a772c7586977af3d32b: Bug 1448439 - Use an accurate pixels per pinch value in AndroidFlingPhysics. r=kats
Botond Ballo <botond@mozilla.com> - Thu, 26 Apr 2018 16:42:05 -0400 - rev 415950
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Use an accurate pixels per pinch value in AndroidFlingPhysics. r=kats MozReview-Commit-ID: I0yZKTvlHWV
68f4c6d260436e8a7d18f3f77de2cb094acc77ff: Bug 1448439 - Expose some of the tunable parameters in AndroidFlingPhysics as prefs. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 20 Apr 2018 18:55:08 -0400 - rev 415949
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Expose some of the tunable parameters in AndroidFlingPhysics as prefs. r=kats MozReview-Commit-ID: J4QRmMdGE0l
9ee2b45eeb3abb0ee922dddfd2adbd47fa4dd261: Bug 1448439 - Add a pref to get APZ to use the Chrome fling physics on Android. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 20 Apr 2018 18:44:18 -0400 - rev 415948
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Add a pref to get APZ to use the Chrome fling physics on Android. r=kats MozReview-Commit-ID: HDLDlwjov82
f6f3318816787873baf0a0c83c90a42bec1f389c: Bug 1448439 - Add an AndroidFlingPhysics class containing an implementation of Chrome's fling physics on Android. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 20 Apr 2018 18:42:08 -0400 - rev 415947
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Add an AndroidFlingPhysics class containing an implementation of Chrome's fling physics on Android. r=kats MozReview-Commit-ID: 509Cl04rozm
da26dcf12417c29b3d1f11e251e088ffb83632c9: Bug 1448439 - Extract a FlingPhysics abstraction from GenericFlingAnimation. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 20 Apr 2018 16:00:11 -0400 - rev 415946
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Extract a FlingPhysics abstraction from GenericFlingAnimation. r=kats The FlingPhysics controls the shape of the fling curve, including how fast and far it goes, while leaving other logic (related to flywheel, handoff, overscroll, etc.) centralized in GenericFlingAnimation. FlingPhysics is a template parameter of GenericFlingAnimation because we already have a dynamic dispatch on the type of the animation, we don't need another one for the physics. I called the specific class implementing the current physics DesktopFlingPhysics because since the deprecation of B2G and Android switching to StackScrollerFlingAnimation, it's only used in desktop touch scenarios. MozReview-Commit-ID: LhJ9rpPrnXC
11540b54a580de5f4bd2d262ed038ccb1ffb6e5e: Bug 1448439 - Move Axis::FlingApplyFrictionOrCancel() to GenericFlingAnimation. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 20 Apr 2018 14:02:38 -0400 - rev 415945
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Move Axis::FlingApplyFrictionOrCancel() to GenericFlingAnimation. r=kats The calculation in that function is specific to a particular physics model, so it's inappropriate to house it in Axis. Also do some light refactoring to this function, to make modifying the velocity the caller's responsibility (this becomes relevant in the next patch, where we factor out the physics logic into a class that can't modify the APZC). MozReview-Commit-ID: 5ALQd3LBx3O
4c88aea1d5d04680ce5264d9dbeff170670c0b0d: Bug 1448439 - Rename AndroidFlingAnimation to StackScrollerFlingAnimation. r=kats
Botond Ballo <botond@mozilla.com> - Tue, 17 Apr 2018 19:56:48 -0400 - rev 415944
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Rename AndroidFlingAnimation to StackScrollerFlingAnimation. r=kats MozReview-Commit-ID: IdvOWYvE9Tr
aa70fd0d1b3cb7232c3146ddf32e4d211c5d4817: Bug 1448439 - Allow the concrete type of fling animations to be determined dynamically. r=kats
Botond Ballo <botond@mozilla.com> - Tue, 17 Apr 2018 19:53:26 -0400 - rev 415943
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Allow the concrete type of fling animations to be determined dynamically. r=kats MozReview-Commit-ID: EBscYyxdlwr
79bbfba09e528f51091c26a84454c0d865f5b466: Bug 1448439 - Fix unified build bustage. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 20 Apr 2018 20:03:52 -0400 - rev 415942
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1448439 - Fix unified build bustage. r=kats MozReview-Commit-ID: 3HAcjOB1tjn
d52b265b6b52a817374add2c4e927530dab571a6: Bug 1457246 - Don't hold the sIndirectLayerTreesLock while making synchronous calls to the RenderBackend thread. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 26 Apr 2018 15:29:21 -0400 - rev 415941
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 1457246 - Don't hold the sIndirectLayerTreesLock while making synchronous calls to the RenderBackend thread. r=sotaro MozReview-Commit-ID: KzXZxCb2nA6
20e6e6da280d51500e980084e17b83e768268b4c: Bug 887889 - Fix intermittent failure in browser_bug419612.js r=mak
Doug Thayer <dothayer@mozilla.com> - Fri, 20 Apr 2018 09:35:40 -0700 - rev 415940
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 887889 - Fix intermittent failure in browser_bug419612.js r=mak MozReview-Commit-ID: 8gp5hdbnzaC
fad1b59c9f557e5d6f09c51b578c2ee9762d26c1: Bug 887889 - Fix leak in RemoteSpellCheckingEngineChild r=Ehsan
Doug Thayer <dothayer@mozilla.com> - Thu, 19 Apr 2018 14:33:18 -0700 - rev 415939
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 887889 - Fix leak in RemoteSpellCheckingEngineChild r=Ehsan The work to migrate to Sqlite.jsm seems to have caused a timing problem in our tests where shutdown the content process while this IPC message is still unresolved. This causes us to destroy RemoteSpellCheckingEngineChild without it having processed its RecvNotiy..., leading to the promise being leaked. As far as I can tell this resolves all of our leak issues on try. MozReview-Commit-ID: GdwVIp5dj1m
6480e870dd73969336b30fb2c0ecfc20c91b3d71: Bug 887889 - Clean up ContentPrefServiceChild on xpcom-shutdown r=mak
Doug Thayer <dothayer@mozilla.com> - Fri, 30 Mar 2018 15:54:08 -0700 - rev 415938
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 887889 - Clean up ContentPrefServiceChild on xpcom-shutdown r=mak I'm not sure why this became necessary as a result of migrating to Sqlite.jsm, but this is the only way I've found to eliminate leaks from the tab process on shutdown. These leaks occur when the child process requests something from the ContentPrefService2 but shuts down before it gets its response. MozReview-Commit-ID: 2Haks17D6Em
7e4a87170569ece8bec68b8163e430ca43937a44: Bug 887889 - Limit scope of executeTransaction closure r=mak
Doug Thayer <dothayer@mozilla.com> - Tue, 27 Mar 2018 10:30:37 -0700 - rev 415937
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 887889 - Limit scope of executeTransaction closure r=mak MozReview-Commit-ID: 9d2xh4Qxs3q
e7f2bc2cb13cbf63ef78ce215d0c393f2bd3ef87: Bug 887889 - Relax Sqlite.jsm restrictions in browser_startup.js r=florian
Doug Thayer <dothayer@mozilla.com> - Mon, 26 Mar 2018 10:08:30 -0700 - rev 415936
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 887889 - Relax Sqlite.jsm restrictions in browser_startup.js r=florian We've improved the startup IO situation in bug 887889 by not synchronously initializing a connection to the contentprefs db. However, this means we are loading Sqlite.jsm earlier than we were, which isn't ideal and can be avoided. However, this isn't completely trivial so I'd like to move this work to a follow-up. MozReview-Commit-ID: 6Em0rN26Qj3
744a7b9fe0abd1095d0f5ba464161d51a97a33b7: Bug 887889 - Asyncify cps2 tests r=mak
Doug Thayer <dothayer@mozilla.com> - Mon, 12 Mar 2018 14:46:24 -0700 - rev 415935
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 887889 - Asyncify cps2 tests r=mak I converted the cps2 tests to use async/await, since it was easier for me to debug the breakages introduced by my changes that way. There are a few differences hidden in there, though - most notable is that I also modified the direct db access in the tests to use the Sqlite.jsm wrapper. This was to avoid reaching into the connections internals in order to get the underlying connection. MozReview-Commit-ID: DwJ5hfyvAOf
29598c587f7fb07c434df30534bdf489f987562d: Bug 887889 - Migrate ContentPrefService2 to Sqlite.jsm r=mak
Doug Thayer <dothayer@mozilla.com> - Mon, 12 Mar 2018 14:41:42 -0700 - rev 415934
Push 33911 by csabou@mozilla.com at Fri, 27 Apr 2018 10:01:39 +0000
Bug 887889 - Migrate ContentPrefService2 to Sqlite.jsm r=mak - I kept the xpcom-shutdown observer around even though it's not doing much and it could be satisfied by doing a little more work in the Sqlite.shutdown blocker. I wasn't sure which to use since it seems like the Sqlite.shutdown blocker is intended to be used to cleanup connection-related things. Thoughts on this are welcome. MozReview-Commit-ID: CqcGHBFaJsZ
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip