54fae0e188b567f8b38d49271e9d91accf7653a2: Bug 1186064 - Require Visual Studio 2015 Update 2; r?glandium draft
Gregory Szorc <gps@mozilla.com> - Tue, 31 May 2016 09:19:00 -0700 - rev 384199
Push 22199 by bmo:gps@mozilla.com at Tue, 05 Jul 2016 19:26:06 +0000
Bug 1186064 - Require Visual Studio 2015 Update 2; r?glandium Per froydnj in bug 1186064 comment #23, "it makes sense to proceed with removing MSVC 2013 support." This commit does that. We also go a step further and require VS2015 Update 2 instead of just update 1. This temporarily brings us down to just 1 officially supported Visual Studio version. However, VS2015u3 was just released and is unofficially supported. Since MOZ_CRT is no longer set, references to it have been removed. MozReview-Commit-ID: 8MUR6qLzQA5
c5214a54cbb6fdaa25cb428a3b17009f0d87bfc5: Bug 1283123 - Reps: make it possible to pass in a component to handle object links. r=linclark,honza draft
Nicolas Chevobbe <chevobbe.nicolas@gmail.com> - Tue, 21 Jun 2016 22:56:10 +0200 - rev 384198
Push 22198 by chevobbe.nicolas@gmail.com at Tue, 05 Jul 2016 19:24:53 +0000
Bug 1283123 - Reps: make it possible to pass in a component to handle object links. r=linclark,honza MozReview-Commit-ID: 20xvwUua4WA
0a3a72e9ecba8af5dc1063c8edb8cdb1546a4ef0: Bug 1226898 - Make autoscroll distance depend on the document height r=pbro
Greg Tatum <tatum.creative@gmail.com> - Tue, 05 Jul 2016 11:52:25 -0700 - rev 384197
Push 22198 by chevobbe.nicolas@gmail.com at Tue, 05 Jul 2016 19:24:53 +0000
Bug 1226898 - Make autoscroll distance depend on the document height r=pbro
29386385b953468a720cbd610c0713a233fb6c46: Bug 1280446 - Create PushService if needed; r=snorp
Jim Chen <nchen@mozilla.com> - Tue, 05 Jul 2016 14:34:57 -0400 - rev 384196
Push 22198 by chevobbe.nicolas@gmail.com at Tue, 05 Jul 2016 19:24:53 +0000
Bug 1280446 - Create PushService if needed; r=snorp If PushService has not been created when getInstance is called, create the PushService instead of throwing an error. This fixes a possible race condition between initializing PushService and receiving a push message, where we can receive a push message first.
3db27bf874fa9e5057b7bcb96f325699bb7f1688: Bug 1256686 - System add-ons should have a more flexible maximum version for easier use with point releases. r=glandium
Mark Banner <standard8@mozilla.com> - Fri, 01 Jul 2016 16:54:18 +0100 - rev 384195
Push 22198 by chevobbe.nicolas@gmail.com at Tue, 05 Jul 2016 19:24:53 +0000
Bug 1256686 - System add-ons should have a more flexible maximum version for easier use with point releases. r=glandium
5abbfd6f277958e00df60b8118280dc24bac6377: Bug 1284482 - Remove useless parameters and variable declarations from _linkBrowserToTab and _createBrowser. r=allassopraise
Dão Gottwald <dao@mozilla.com> - Tue, 05 Jul 2016 18:52:40 +0200 - rev 384194
Push 22198 by chevobbe.nicolas@gmail.com at Tue, 05 Jul 2016 19:24:53 +0000
Bug 1284482 - Remove useless parameters and variable declarations from _linkBrowserToTab and _createBrowser. r=allassopraise
226e279a1016a5b10ac0a62b5282ca03f8c72566: Bug 1213517 - Wire up getSettings(). draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Mon, 20 Jun 2016 00:38:25 -0400 - rev 384193
Push 22197 by jbruaroey@mozilla.com at Tue, 05 Jul 2016 19:22:56 +0000
Bug 1213517 - Wire up getSettings(). MozReview-Commit-ID: EX5FIo3rCoi
4415a9e3a056994da335c4f1605bcd89e14f42b5: Bug 1213517 - Let cam access in competing tabs get closer to their ideals when a tab closes. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Sat, 18 Jun 2016 19:09:39 -0400 - rev 384192
Push 22197 by jbruaroey@mozilla.com at Tue, 05 Jul 2016 19:22:56 +0000
Bug 1213517 - Let cam access in competing tabs get closer to their ideals when a tab closes. MozReview-Commit-ID: htWkYMm18U
836a4998cfaae03913393c94a08184743b9adddd: Bug 1213517 - Consolidate camera Allocate's and Restart's constraints logic. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Sat, 18 Jun 2016 16:11:54 -0400 - rev 384191
Push 22197 by jbruaroey@mozilla.com at Tue, 05 Jul 2016 19:22:56 +0000
Bug 1213517 - Consolidate camera Allocate's and Restart's constraints logic. MozReview-Commit-ID: CrARq0QZzrO
4fc71754ac6d3622d13e65cb323f07b88b5e8b4e: Bug 1213517 - Only restart camera if net settings actually change. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Sat, 18 Jun 2016 14:16:47 -0400 - rev 384190
Push 22197 by jbruaroey@mozilla.com at Tue, 05 Jul 2016 19:22:56 +0000
Bug 1213517 - Only restart camera if net settings actually change. MozReview-Commit-ID: h01gJ3uCom
6b11ff4b546f1722d22e61b4c8495c5162de0a28: Bug 1213517 - Lift correct constraint out of lower-level code for OverconstrainedError. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Mon, 20 Jun 2016 20:15:39 -0400 - rev 384189
Push 22197 by jbruaroey@mozilla.com at Tue, 05 Jul 2016 19:22:56 +0000
Bug 1213517 - Lift correct constraint out of lower-level code for OverconstrainedError. MozReview-Commit-ID: EWUjVBUrAps
54e2ed5a531b540f6f7adde4639000fa446db25a: Bug 1213517 - Normalize even more of the constraints code. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Fri, 17 Jun 2016 15:20:10 -0400 - rev 384188
Push 22197 by jbruaroey@mozilla.com at Tue, 05 Jul 2016 19:22:56 +0000
Bug 1213517 - Normalize even more of the constraints code. MozReview-Commit-ID: 1XjdHXKYOmP
bfe7c6aad72ed3934afb7f4767a31a63ff430bd6: Bug 1213517 - optimize for maintenance of constraints (member pointer approach). draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Mon, 27 Jun 2016 10:03:27 -0400 - rev 384187
Push 22197 by jbruaroey@mozilla.com at Tue, 05 Jul 2016 19:22:56 +0000
Bug 1213517 - optimize for maintenance of constraints (member pointer approach). MozReview-Commit-ID: 4JYb6QnMtVk
047c1b9289f6822775a9c55569dd62b70e3d789a: Bug 1213517 - Report correct constraint in OverconstrainedError when constraints conflict directly. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Wed, 15 Jun 2016 19:25:07 -0400 - rev 384186
Push 22197 by jbruaroey@mozilla.com at Tue, 05 Jul 2016 19:22:56 +0000
Bug 1213517 - Report correct constraint in OverconstrainedError when constraints conflict directly. MozReview-Commit-ID: 2bVaSvntc8g
7625ddbcf2a2dc6a3b7d1574975854c5a7cce5c0: Bug 1284013 - Part 2 - Reduce session store save delays when in background. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 17 Apr 2016 22:06:06 +0200 - rev 384185
Push 22196 by mozilla@buttercookie.de at Tue, 05 Jul 2016 19:20:51 +0000
Bug 1284013 - Part 2 - Reduce session store save delays when in background. r=margaret When we are backgrounded and Android's onPause() handler runs, we try to synchronously flush out any pending session store to storage. If however some tab events (e.g. tab closing) have been dispatched shortly before the application backgrounding, it is possible that they'll arrive at the session store after the "application-background" event. In this case, we need to process and write them to storage as fast as possible, as we can be killed at any moment now. Therefore the delay between successive writes is completely abolished while the application is in background. The minimum delay between a call to saveStateDelayed() and a write operation however is not completely eliminated and instead only reduced to 200 ms, so as to allow for closely following tab events (e.g. closing a tab involves both a TabSelect and TabClose event) to be batched together in one write operation. MozReview-Commit-ID: I8q7z4kll7O
bc6188cbb7318827fbed54fd8cce6415f175450b: Bug 1280510 - Copy hi/lo dpi loading icon from windows to Linux. r?dao draft
Eitan Isaacson <eitan@monotonous.org> - Fri, 01 Jul 2016 14:18:44 -0700 - rev 384184
Push 22195 by bmo:eitan@monotonous.org at Tue, 05 Jul 2016 19:18:31 +0000
Bug 1280510 - Copy hi/lo dpi loading icon from windows to Linux. r?dao MozReview-Commit-ID: FraPEDKnQAQ
1a90d3f06532141417e862a0b1c94d3043b2fac5: Bug 1280135 - Make hidpi version of search-indicator icon work on Linux. r?florian draft
Eitan Isaacson <eitan@monotonous.org> - Tue, 14 Jun 2016 22:57:07 +0100 - rev 384183
Push 22194 by bmo:eitan@monotonous.org at Tue, 05 Jul 2016 19:16:19 +0000
Bug 1280135 - Make hidpi version of search-indicator icon work on Linux. r?florian MozReview-Commit-ID: Fo7NlMOiRoJ
55e9cfd7babc572d21a1e12a342dd914ee2e41d6: Bug 1284013 - Part 3 - Reduce session store save delays when in background. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 17 Apr 2016 22:06:06 +0200 - rev 384182
Push 22193 by mozilla@buttercookie.de at Tue, 05 Jul 2016 19:16:14 +0000
Bug 1284013 - Part 3 - Reduce session store save delays when in background. r=margaret When we are backgrounded and Android's onPause() handler runs, we try to synchronously flush out any pending session store to storage. If however some tab events (e.g. tab closing) have been dispatched shortly before the application backgrounding, it is possible that they'll arrive at the session store after the "application-background" event. In this case, we need to process and write them to storage as fast as possible, as we can be killed at any moment now. Therefore the delay between successive writes is completely abolished while the application is in background. The minimum delay between a call to saveStateDelayed() and a write operation however is not completely eliminated and instead only reduced to 200 ms, so as to allow for closely following tab events (e.g. closing a tab involves both a TabSelect and TabClose event) to be batched together in one write operation. MozReview-Commit-ID: I8q7z4kll7O
b79b44db1fbcb7edccc589308ad1d3b091e9b17e: Bug 1284013 - Part 2 - Defer writes if there's already an async write in progress. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 17 Apr 2016 21:41:32 +0200 - rev 384181
Push 22193 by mozilla@buttercookie.de at Tue, 05 Jul 2016 19:16:14 +0000
Bug 1284013 - Part 2 - Defer writes if there's already an async write in progress. r=margaret Currently, it is possible for a second write (sync or async) to be requested while a previous async write operation is still in progress. This might lead to undesired results if the second write is then completed before the first write, or if a sync write is interfering with a parallel async write operation. The only guard against a second async write is the minimum delay of 2 s between successive async writes enforced in saveStateDelayed(); there is no guard against sync writes. To avoid data loss when the application is backgrounded, it is desirable to reduce or completely eliminate this minimum delay (see Part 3), therefore we need to devise alternative means of ensuring that successive writes won't interfere with each other. With this patch, only one save operation is allowed to execute within _saveState() at the same time. Successive calls to _saveState() will be deferred, coalesced into one operation and executed once the previous async write returns from _writeFile()'s promise callback. Sync writes take priority, so if any of the deferred calls to _saveState() is a sync write, the resulting operation will be a sync write, too. This has the slight drawback that we can't execute truly synchronously within Android's onPause() call if an async state save is already in progress, however this should occur only very occasionally and is probably still more desirable than a possible write collision with a previous async state save. MozReview-Commit-ID: G2eogo1z8vr
7bb92418ebeeabd9abf45ea2e3e3a7f6c9a048a8: Bug 1284013 - Part 1 - Use temp file for synchronous writes, too. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 17 Apr 2016 18:22:36 +0200 - rev 384180
Push 22193 by mozilla@buttercookie.de at Tue, 05 Jul 2016 19:16:14 +0000
Bug 1284013 - Part 1 - Use temp file for synchronous writes, too. r=margaret Currently, sync writes go directly to the destination file, so an interrupted write will leave the session store data in an inconsistent state. To minimise the incidence of this occurring as far as possible, we now mimic the behaviour of atomicWrite when a tmpPath is set and write to a temporary file which is then renamed to the actual destination file after writing has finished. MozReview-Commit-ID: 3f3z1s0hfl8
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip