e151f125df063f6ffb4c462f603088a5909c2db5: Bug 1472646 [wpt PR 11751] - Add an instance of ImageData to the HTML interfaces test., a=testonly
Ms2ger <Ms2ger@gmail.com> - Fri, 09 Nov 2018 15:45:13 +0000 - rev 445563
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1472646 [wpt PR 11751] - Add an instance of ImageData to the HTML interfaces test., a=testonly Automatic update from web-platform-testsAdd an instance of ImageData to the HTML interfaces test. This causes the test to catch a bug in WebKit, where it defines a "data" property on the instance, along with the correct property on the prototype. -- wpt-commits: e7709bb04369254cf0aca11a869a23e1963abdef wpt-pr: 11751
d3969902dc5ab882b9c7e27dc1081af8770865b5: Bug 1501228 [wpt PR 13676] - Update docker image to Ubuntu 18.04, a=testonly
jgraham <james@hoppipolla.co.uk> - Fri, 09 Nov 2018 15:45:11 +0000 - rev 445562
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1501228 [wpt PR 13676] - Update docker image to Ubuntu 18.04, a=testonly Automatic update from web-platform-testsUpdate docker image to Ubuntu 18.04 (#13676) This is the latest LTS release, so it makes sense to test on it. Also it is a requirement to get servo builds running in the docker image since 16.04 has a too-old gstreamer. -- wpt-commits: fbc56f388ac5d3a9cfcdfc161917ba0cfa2280f5 wpt-pr: 13676
9f204d50bec7fdf559885b75786ec4587a3bf7a3: Merge mozilla-central to mozilla-inbound. a=merge
Razvan Maries <rmaries@mozilla.com> - Sat, 10 Nov 2018 02:24:04 +0200 - rev 445561
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Merge mozilla-central to mozilla-inbound. a=merge
6a126cf9ca31a33c756aa83ec951b6e48411cfa1: Bug 1504031 - follow-up - require Rust 1.30.1 in bootstrap; r=me
Nathan Froyd <froydnj@mozilla.com> - Fri, 09 Nov 2018 18:47:37 -0500 - rev 445560
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1504031 - follow-up - require Rust 1.30.1 in bootstrap; r=me
999652c2fc2b9b0df22c77c925160c1a22f686ea: Second attempt to fix Bug 1505790 - Fix intermittent failure of browser_updatesBackgroundWindow.js. r=bytesize
Robert Strong <robert.bugzilla@gmail.com> - Fri, 09 Nov 2018 15:39:34 -0800 - rev 445559
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Second attempt to fix Bug 1505790 - Fix intermittent failure of browser_updatesBackgroundWindow.js. r=bytesize The failure is in the sync code and setting services.sync.autoconnectDelay to a large value should prevent this failure.
d33d5a71940366ca9d0ed7609dc5dfac2c5a9355: Backed out changeset c9bd800631be (bug 1503560) for perma failing browser_trackingUI_fetch.js, test_bug1274685_unowned_list.js CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Sat, 10 Nov 2018 01:06:39 +0200 - rev 445558
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Backed out changeset c9bd800631be (bug 1503560) for perma failing browser_trackingUI_fetch.js, test_bug1274685_unowned_list.js CLOSED TREE
111655db0b164cbf3eaaac6feccf3c98e8d8066d: Backed out changeset 0abbc0f316d3 (Bug 1505271) for raptor perma failures CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Sat, 10 Nov 2018 00:52:55 +0200 - rev 445557
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Backed out changeset 0abbc0f316d3 (Bug 1505271) for raptor perma failures CLOSED TREE *** Backed out changeset dfdd63aae0c5 (bug 1505271) for raptor perma failures CLOSED TREE
c9bd800631be838f0f9f99f31ff6b58ef5f407f5: Bug 1503560 - [1.1] Override tracking protection pref on GeckoView to re-enable blocklist updates. r=francois
Eugen Sawin <esawin@mozilla.com> - Fri, 09 Nov 2018 16:54:37 +0100 - rev 445556
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1503560 - [1.1] Override tracking protection pref on GeckoView to re-enable blocklist updates. r=francois
305c901c0ebb48592bf1c7c41c6980489fbb23a7: Bug 1506019 - Handle close() calls after diverging from the recording, r=lsmyth.
Brian Hackett <bhackett1024@gmail.com> - Fri, 09 Nov 2018 10:19:18 -1000 - rev 445555
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1506019 - Handle close() calls after diverging from the recording, r=lsmyth.
d2013de59e87ff63899ef1e634bd3889ec126c93: Bug 1505777: Run mach-vendor-rust to update Cranelift. rs=bbouvier
Dan Gohman <sunfish@mozilla.com> - Fri, 09 Nov 2018 05:16:08 -0800 - rev 445554
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1505777: Run mach-vendor-rust to update Cranelift. rs=bbouvier
4fb48d47b208c85fad068711fd78b189b6fee88c: Bug 1505777: [Cranelift] Use the Cranelift global values for tables. r=bbouvier
Dan Gohman <sunfish@mozilla.com> - Fri, 09 Nov 2018 05:16:07 -0800 - rev 445553
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1505777: [Cranelift] Use the Cranelift global values for tables. r=bbouvier
3d3fb1fce6a998fdb79c7523610cc5a9a3cf6a96: Bug 1505777: [Cranelift] Update to Cranelift 0.23. r=bbouvier
Dan Gohman <sunfish@mozilla.com> - Fri, 09 Nov 2018 05:15:49 -0800 - rev 445552
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1505777: [Cranelift] Update to Cranelift 0.23. r=bbouvier
1395bbfd01b8b5ac84862684026f59ffa45cd46a: Bug 1506224 - Update pdf.js to version 2.1.42. r=bdahl
Ryan VanderMeulen <ryanvm@gmail.com> - Fri, 09 Nov 2018 14:31:08 -0500 - rev 445551
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1506224 - Update pdf.js to version 2.1.42. r=bdahl
4bf1c95a5db3496554813b3c333296e759138510: Bug 1503724 - Fix progress bar on first load in Fennec custom tabs. r=esawin
Dylan Roeh <droeh@mozilla.com> - Fri, 09 Nov 2018 08:58:32 -0600 - rev 445550
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1503724 - Fix progress bar on first load in Fennec custom tabs. r=esawin There's a race condition here where we receive STATE_START before we've enabled GeckoViewProgressChild; this patch starts listening for web progress in onInit() rather than onEnable() so that we can guarantee progress tracking will work whenever a ProgressDelegate is set.
3787e34b3595ab7c5c929bc5928c92f04a43a176: Bug 1506180 - part 2 - delete VS2015 mozconfigs; r=RyanVM
Nathan Froyd <froydnj@mozilla.com> - Fri, 09 Nov 2018 14:04:29 -0500 - rev 445549
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1506180 - part 2 - delete VS2015 mozconfigs; r=RyanVM We no longer support MSVC 2015.
0698821c5ebdc6e124cab849a332650f5ac2f895: Bug 1506180 - part 1 - factor out a win_sdk_version variable; r=RyanVM
Nathan Froyd <froydnj@mozilla.com> - Fri, 09 Nov 2018 14:04:29 -0500 - rev 445548
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1506180 - part 1 - factor out a win_sdk_version variable; r=RyanVM This change makes the lines a little longer, but ideally makes changes easier and nicer to read.
4e5d78c219f5ba5917c33ad033a0ea857f422488: Bug 1495749 - Allow add-ons to be updated via policy by uninstalling and reinstalling them. r=mkaply
Felipe Gomes <felipc@gmail.com> - Fri, 09 Nov 2018 17:01:18 -0200 - rev 445547
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1495749 - Allow add-ons to be updated via policy by uninstalling and reinstalling them. r=mkaply
71df0988d340789d2a6fb26edb36936947b543c8: Bug 1429488 - Part 8: Fix mobile about:addons code for enabling/disabling themes. r=aswan
Jan Henning <jh+bugzilla@buttercookie.de> - Thu, 01 Nov 2018 22:08:59 +0100 - rev 445546
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1429488 - Part 8: Fix mobile about:addons code for enabling/disabling themes. r=aswan about:addons on Android has some logic to ensure that only one theme can be active at the same time. At some point however, themes must have learned to take care of themselves in that regard, which means that this code a) has become unnecessary, and b) with Webextension themes it can actually cause a harmful race condition: Explicitly disabling the previously active theme implicitly enables the default theme, so what happens is that depending on the size of the Webextension theme to be enabled, the new theme can be enabled before the previous disable() call completes. This leads to the new theme then immediately being disabled again as the previous disable() call finally gets around to enabling the default theme. The smaller the Webextension theme to be enabled and the faster it loads, the more likely this is to happen. We still need to manually fix up the disabled state of themes in the UI, though, so that it shows the correct state without a reload. Therefore, we take the opportunity to fix the problem that up until now, disabling a theme wouldn't mark the default theme as enabled in the UI, unless you manually reloaded the page afterwards. Differential Revision: https://phabricator.services.mozilla.com/D10732
9e24466d3f963ab7829331469c241ab242fe2cf1: Bug 1429488 - Part 7: Move responsibility for persisting themes on Android to LWTConsumer. r=jaws
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 31 Oct 2018 20:38:26 +0100 - rev 445545
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1429488 - Part 7: Move responsibility for persisting themes on Android to LWTConsumer. r=jaws We intercept the theme data just before sending it to the front-end in order to fix it up as described in part 4. There is one snag, though: When the theme data processed in Android's LightweightThemeConsumer isn't fresh data received via lightweight-theme- styling-update, but instead a theme retrieved via LWTManager .currentThemeForDisplay, we risk passing already persisted theme data to LWTPersister.persistImages(). When the LWTPersister encounters an image which already has a file:// URI, it just skips it and doesn't call the success callback in that case, which means we never execute the rest of the code to pass the data on to the Android front-end. Even if it did, this would mean we'd be calling LWTPersister.getPersistedData() twice: Once implicitly through asking for currentThemeForDisplay, and a second time explicitly. So instead, we're asking the LWTManager for currentThemeWithFallback, which returns the original theme data, which we can then safely pass to persistImages() and fix up ourselves through getPersistedData(). This introduces a different problem, though: If the same theme has previously already been successfully persisted, we'd be unnecessarily persisting it again, and even worse, we'd do that on each startup. To avoid that, we make the LWTPersister store and then check the persisted theme's ID and version. If they have remained unchanged, we can short-circuit the call to persistImages and immediately declare success. Differential Revision: https://phabricator.services.mozilla.com/D10731
116776356ba267214cc299371d023e7c5f26ec05: Bug 1429488 - Part 6: Include some metadata in LWT data extracted from static themes. r=jaws
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 31 Oct 2018 20:37:26 +0100 - rev 445544
Push 35020 by shindli@mozilla.com at Sat, 10 Nov 2018 21:37:25 +0000
Bug 1429488 - Part 6: Include some metadata in LWT data extracted from static themes. r=jaws To optimise the behaviour of the LightweightThemePersister, we want the ID and version of the theme that we want to persist to be available for static themes, too. Differential Revision: https://phabricator.services.mozilla.com/D10730
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip