ab31927770b8dad266d2e4db97e095aa63bfeb89: Bug 1490493 - 2. Add tests for GeckoView saving/restoring state; r=droeh
Jim Chen <nchen@mozilla.com> - Fri, 14 Sep 2018 14:47:25 -0400 - rev 436487
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1490493 - 2. Add tests for GeckoView saving/restoring state; r=droeh Add some tests for all scenarios that GeckoView encounters when it is saving/restoring state. Differential Revision: https://phabricator.services.mozilla.com/D5607
8a0955e0457ac8279241a568bbc97b8fdb2d9bb3: Bug 1490493 - 1. Return early if same session is being restored; r=droeh
Jim Chen <nchen@mozilla.com> - Fri, 14 Sep 2018 14:47:24 -0400 - rev 436486
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1490493 - 1. Return early if same session is being restored; r=droeh Restoring the same session that's already managed by the GeckoView instance should be a no-op. Differential Revision: https://phabricator.services.mozilla.com/D5606
32efa2eb33bd3a1fbce801a6fcebe8e9411bfd2d: Bug 1485810 - 2. Add GeckoViewAutoFill support in browser.js; r=petru
Jim Chen <nchen@mozilla.com> - Fri, 14 Sep 2018 14:46:27 -0400 - rev 436485
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1485810 - 2. Add GeckoViewAutoFill support in browser.js; r=petru Make auto-fill work for the main Fennec activity by making calls to GeckoViewAutoFill. Differential Revision: https://phabricator.services.mozilla.com/D4804
d59d980a57453bd4ee0cf1b3ec527700e3304e88: Bug 1485810 - 1. Move auto-fill code to GeckoViewAutoFill.jsm; r=droeh
Jim Chen <nchen@mozilla.com> - Fri, 14 Sep 2018 14:46:25 -0400 - rev 436484
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1485810 - 1. Move auto-fill code to GeckoViewAutoFill.jsm; r=droeh Move all auto-fill code to GeckoViewAutoFill.jsm, so they can be shared between GeckoView and Fennec. Differential Revision: https://phabricator.services.mozilla.com/D4803
1a98e90a6464d389bc544ba1c2f01a9774882c17: Merge mozilla-central to inbound. a=merge CLOSED TREE
Gurzau Raul <rgurzau@mozilla.com> - Fri, 14 Sep 2018 21:15:54 +0300 - rev 436483
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Merge mozilla-central to inbound. a=merge CLOSED TREE
9762d76da9b33ab583c4e89b4fb642be6fadb981: Bug 1480293 - Basic Memory Reporting for WebRender. r=jrmuizel
Bobby Holley <bobbyholley@gmail.com> - Fri, 07 Sep 2018 16:03:13 -0700 - rev 436482
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1480293 - Basic Memory Reporting for WebRender. r=jrmuizel Reviewers: jrmuizel, gw Tags: #secure-revision Bug #: 1480293 Differential Revision: https://phabricator.services.mozilla.com/D5719 MozReview-Commit-ID: 1vGl3890CjR
1cff3816f35ac450f103aa1a8c017afce69cba01: Bug 1480854 - Use classic icons again on platforms prior to Oreo. r=jchen
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 08 Sep 2018 18:30:30 +0200 - rev 436481
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1480854 - Use classic icons again on platforms prior to Oreo. r=jchen We want to use the classic, non-adaptive icon again as our launcher icon on Android versions prior to Oreo, as well as to continue using it in various places within our app. Unfortunately this means that we still have to provide duplicate resources for those two purposes: Because we don't want to use the adaptive icon internally, we can't use the same resource directly for both internal usage and our launcher icon, because other- wise on Oreo and above we'd receive the adaptive icon that way. One possible workaround would have been to use the PNG files of our classic icon directly as a drawable for internal useage and then create a differently named XML bitmap for our launcher icon, which in turn would be overridden by the adaptive icon on Oreo and above. Unfortunately, modern usage demands that the launcher icon should be provided as a mipmap resource, where XML bitmaps - aren't officially supported - unofficially work with some devices/launchers, but not all. Therefore, our only choice is to provide separate drawables for our internal icon and our launcher icon, even if prior to Android O both will have the same contents. We'll also get rid of the separate round icon again, since - on Android O and above, both round and non-round icons were using the same adaptive icon anyway - prior to Android O our normal icon is already round enough, but not round enough to pass the lint check
d212d02b75014a20afed1b4eb61ee80fd85a3769: Bug 1491130. Update webrender to commit da76f6aad61c1ba769566861ec41b42d511fa456
Jeff Muizelaar <jmuizelaar@mozilla.com> - Fri, 14 Sep 2018 13:39:33 -0400 - rev 436480
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1491130. Update webrender to commit da76f6aad61c1ba769566861ec41b42d511fa456
85c0ed4ef9c07f9ed83e1279c1c0b4479881b74c: Bug 1473921 - Load checkbox.css and radio.css as document stylesheets. r=paolo
Dão Gottwald <dao@mozilla.com> - Fri, 14 Sep 2018 19:35:47 +0200 - rev 436479
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1473921 - Load checkbox.css and radio.css as document stylesheets. r=paolo
f8bf4f08ececa908442535c90aa44e60712039c6: Bug 1491019 - Remove the XPCOM component registration for nsXULControllers; r=baku
Ehsan Akhgari <ehsan@mozilla.com> - Thu, 13 Sep 2018 11:02:50 -0400 - rev 436478
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1491019 - Remove the XPCOM component registration for nsXULControllers; r=baku Differential Revision: https://phabricator.services.mozilla.com/D5774
5f9d6d1fa6cc95f9906c3eecf5ef61eb6561c55e: Bug 1491378 - Update pdf.js to version 2.0.854. r=bdahl
Ryan VanderMeulen <ryanvm@gmail.com> - Fri, 14 Sep 2018 13:02:33 -0400 - rev 436477
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1491378 - Update pdf.js to version 2.0.854. r=bdahl
0e38d6dfc780656f74959704929a037871503548: Backed out changeset 56f980324015 (bug 1480854) for lint bustage. CLOSED TREE
Narcis Beleuzu <nbeleuzu@mozilla.com> - Fri, 14 Sep 2018 19:22:52 +0300 - rev 436476
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Backed out changeset 56f980324015 (bug 1480854) for lint bustage. CLOSED TREE
b5050dd99c1456f97240ef208aecf9d641261470: Backed out changeset 433f1ab89061 (bug 1491257) for xpcshell failures on test_sync.js. CLOSED TREE
Narcis Beleuzu <nbeleuzu@mozilla.com> - Fri, 14 Sep 2018 19:16:11 +0300 - rev 436475
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Backed out changeset 433f1ab89061 (bug 1491257) for xpcshell failures on test_sync.js. CLOSED TREE
98343cbec0c4734ce751547612a34f82b7b9e661: Bug 1384557 - move _DEPEND_CFLAGS+CL_INCLUDES_PREFIX to toolchain.configure, ignore {CC,CXX}_WRAPPER when using sccache; r=glandium
Ted Mielczarek <ted@mielczarek.org> - Fri, 14 Sep 2018 12:12:34 -0400 - rev 436474
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1384557 - move _DEPEND_CFLAGS+CL_INCLUDES_PREFIX to toolchain.configure, ignore {CC,CXX}_WRAPPER when using sccache; r=glandium Currently mozconfig.cache overrides a few build options for sccache. This patch moves them into toolchain.configure so that the build system will set them properly when sccache is in use. Additionally, {CC,CXX}_WRAPPER are set in config.mk, so just avoid setting them when sccache is in use.
56f9803240157892066fa5b1703b8fe50c28020d: Bug 1480854 - Use classic icons again on platforms prior to Oreo. r=jchen
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 08 Sep 2018 18:30:30 +0200 - rev 436473
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1480854 - Use classic icons again on platforms prior to Oreo. r=jchen We want to use the classic, non-adaptive icon again as our launcher icon on Android versions prior to Oreo, as well as to continue using it in various places within our app. Unfortunately this means that we still have to provide duplicate resources for those two purposes: Because we don't want to use the adaptive icon internally, we can't use the same resource directly for both internal usage and our launcher icon, because other- wise on Oreo and above we'd receive the adaptive icon that way. One possible workaround would have been to use the PNG files of our classic icon directly as a drawable for internal useage and then create a differently named XML bitmap for our launcher icon, which in turn would be overridden by the adaptive icon on Oreo and above. Unfortunately, modern usage demands that the launcher icon should be provided as a mipmap resource, where XML bitmaps - aren't officially supported - unofficially work with some devices/launchers, but not all. Therefore, our only choice is to provide separate drawables for our internal icon and our launcher icon, even if prior to Android O both will have the same contents. We'll also get rid of the separate round icon again, since - on Android O and above, both round and non-round icon were using the same adaptive icon anyway - prior to Android O our normal icon is already round enough (ignoring the Fennec icon for local developer builds)
0007350858da8be409c61de5ac2255faa2e19b70: Merge mozilla-central to inbound. a=merge CLOSED TREE
Brindusan Cristian <cbrindusan@mozilla.com> - Fri, 14 Sep 2018 18:31:01 +0300 - rev 436472
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Merge mozilla-central to inbound. a=merge CLOSED TREE
433f1ab8906128b92811ccbc68a03c387527d9bf: bug 1491257: marionette: make PollPromise more precise; r=whimboo
Andreas Tolfsen <ato@sny.no> - Fri, 14 Sep 2018 12:43:15 +0100 - rev 436471
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
bug 1491257: marionette: make PollPromise more precise; r=whimboo A PollPromise with timeout of 100 ms and interval of 100 ms is normally expected to fire twice: once immediately and once before the timeout at 100 ms. On slow systems, such as Windows PGO TV, the timeout timer may be slow enough for a third evaluation of the PollPromise to occur. By making the timer strategy more precise we can ensure that the repeating timer has a constant period between firings. This guarantees that it will not queue up new events to fire the callback until the previous callback event finishes. This means, that if the callback takes a long time to evaluate, the next evaluation is only scheduled after it returns. This will prevent firings to happen after the timeout duration has elapsed.
302dcd8139426cfe25b9d2685800809c2d603658: Bug 1485420 - Part 2. Make ClipManager trim clip chains which can be merged with the display item. r=mstange
Andrew Osmond <aosmond@mozilla.com> - Fri, 14 Sep 2018 10:42:23 -0400 - rev 436470
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1485420 - Part 2. Make ClipManager trim clip chains which can be merged with the display item. r=mstange
a3ea43b5e6d882d9fa8b4477c654e76f5b6e6f7a: Bug 1485420 - Part 1. Expose WebRender bindings to merge a clip rect with a display item. r=mstange
Andrew Osmond <aosmond@mozilla.com> - Fri, 14 Sep 2018 10:42:20 -0400 - rev 436469
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1485420 - Part 1. Expose WebRender bindings to merge a clip rect with a display item. r=mstange This part allows the caller to push a clip rect onto a stack that will be used with any display items added to DisplayListBuilder. Said rect will be intersected with the given clip rect for the display item (if applicable).
be6801cdeb537afa655bbd67d12ead8dc01c6c38: Bug 1490886 - [wpt-sync] Update web-platform-tests to 9a16eee96e7fb06c7ca05899436e35c957e676d8, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 13 Sep 2018 03:02:39 +0000 - rev 436468
Push 34645 by dluca@mozilla.com at Sat, 15 Sep 2018 09:47:39 +0000
Bug 1490886 - [wpt-sync] Update web-platform-tests to 9a16eee96e7fb06c7ca05899436e35c957e676d8, a=testonly wpt-head: 9a16eee96e7fb06c7ca05899436e35c957e676d8 wpt-type: landing
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip