16d8a19df81393398075c6f4695d9a55b96b55d2: Bug 1525402 - Manual fixups for configs cargo fix missed. r=kvark
Alexis Beingessner <a.beingessner@gmail.com> - Tue, 07 May 2019 01:40:21 +0000 - rev 472820
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1525402 - Manual fixups for configs cargo fix missed. r=kvark cargo fix works by building under a specific config, so we can't hit both sides of a mutually exclusive pair of cfgs, such as cfg(target_os) or when cfg(feature) and cfg(not(feature)) both exist in the codebase. Differential Revision: https://phabricator.services.mozilla.com/D29568
8c7d885ae03623bf540a6d31372b5585e2aabcab: Bug 1525402 - Migrate webrender externs to a Rust 2018 compatible form. r=kvark
Alexis Beingessner <a.beingessner@gmail.com> - Tue, 07 May 2019 01:40:19 +0000 - rev 472819
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1525402 - Migrate webrender externs to a Rust 2018 compatible form. r=kvark Notably `extern crate foo as bar` is no longer supported (must do it in Cargo.toml). Also stopped using euclid through webrender_api, because it produces worse results in 2018. Differential Revision: https://phabricator.services.mozilla.com/D29566
0c2296965b7b07a50a8b8a643de442f03f196b27: Bug 1525402 - Bump cargo-vendor to 0.1.23. r=kats
Alexis Beingessner <a.beingessner@gmail.com> - Tue, 07 May 2019 01:40:17 +0000 - rev 472818
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1525402 - Bump cargo-vendor to 0.1.23. r=kats 0.1.21 mishandles cargo package renames, which are a required feature for Rust 2018 support. The latest version fixes this. Differential Revision: https://phabricator.services.mozilla.com/D29946
ddce4ed9bb05e90f16187c66c798737110ca4be9: Bug 1525402 - Bump cbindgen to 0.8.6. r=kvark
Alexis Beingessner <a.beingessner@gmail.com> - Tue, 07 May 2019 01:40:15 +0000 - rev 472817
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1525402 - Bump cbindgen to 0.8.6. r=kvark This version adds support for Rust 2018's new externs Differential Revision: https://phabricator.services.mozilla.com/D29565
5ce032a6115e0ff4980487738194cbaf83a8585d: Bug 1544971. Provide some more documention about nsView's. r=jwatt
Timothy Nikkel <tnikkel@gmail.com> - Tue, 07 May 2019 01:30:33 +0000 - rev 472816
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1544971. Provide some more documention about nsView's. r=jwatt Differential Revision: https://phabricator.services.mozilla.com/D27837
90ebd256a92b6abfa5a701dfac54b40e45ca3351: Bug 1540573 - p7. Modify CSP tests to use preload=2 on (emulated) cellular connections. r=jya
Chris Pearce <cpearce@mozilla.com> - Mon, 06 May 2019 22:43:18 +0000 - rev 472815
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1540573 - p7. Modify CSP tests to use preload=2 on (emulated) cellular connections. r=jya The Content Security Policy tests were handling the smaller android preload values that were #defined on Android by setting media.preload.default=2. Now that we're detecting whether we're on cellular or not, and the android emulators that our tests run on emulate a cellular connection, just setting media.preload.default is no longer enough. So set media.preload.default.cellular=2 in the CSP mochitests instead of media.preload.default, to make the CSP mochitests pass in the Android emulators. Differential Revision: https://phabricator.services.mozilla.com/D29617
0d175912734db128b3f4fc4dab37a10997d17852: Bug 1540573 - P6. Use frugal preloading of media data when on cellular, otherwise aggressive. r=jya
Chris Pearce <cpearce@mozilla.com> - Mon, 06 May 2019 22:43:14 +0000 - rev 472814
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1540573 - P6. Use frugal preloading of media data when on cellular, otherwise aggressive. r=jya We're allowed to take some liberties as to what the default value and behaviour we assume for the 'preload' attribute on HTMLMediaElement by the spec. On desktop we assumed preload="metadata", while on mobile we assumed the default of preload="none" to save data. On mobile we also assumed that preload="auto" meant preload="metadata". I think it makes sense to instead of always assuming that data on Android is always expensive, we can instead detect if we're running on a cellular connection, and preload frugally then, otherwise aggressively. Differential Revision: https://phabricator.services.mozilla.com/D26235
07c6d54744f70517f1d5d92789c44335631229da: Bug 1540573 - P5. Only "always throttle" media download to the readahead on cellular connections. r=jya
Chris Pearce <cpearce@mozilla.com> - Mon, 06 May 2019 22:43:09 +0000 - rev 472813
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1540573 - P5. Only "always throttle" media download to the readahead on cellular connections. r=jya Normally when downloading media data we throttle the download only if we're ahead of the read cursor more than the "readahead limit", and if we estimate that the connection is fast enough that we'll be able to download at a rate fast enough to playback in real time if we resume it later. On mobile we additionally override this so that we always throttle the download once we're ahead of the read cursor by the readahead limit. This is to save data. I think we can relax this to only do this override if we're on a cellular connection; if we're on WiFi we can assume data is cheap. Differential Revision: https://phabricator.services.mozilla.com/D26234
bcbb8c779852193d99648b9a109daf5ffe17058a: Bug 1540573 - P4. Use larger MediaCache sizes when on cellular connection. r=jya
Chris Pearce <cpearce@mozilla.com> - Mon, 06 May 2019 23:38:02 +0000 - rev 472812
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1540573 - P4. Use larger MediaCache sizes when on cellular connection. r=jya Differential Revision: https://phabricator.services.mozilla.com/D26233
b78948e4f480ea6b99f2c689fe048256590b8769: Bug 1540573 - P3. Expose network link type on ContentChild for use in content process. r=snorp
Chris Pearce <cpearce@mozilla.com> - Mon, 06 May 2019 22:41:25 +0000 - rev 472811
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1540573 - P3. Expose network link type on ContentChild for use in content process. r=snorp In GeckoView the nsINetworkLinkService doesn't work in the content process, as we don't seem to have an AndroidBridge there, so just maintain the network connection type on the ContentChild. (I had considered keeping this on the NeckoChild, but the creation of that is initiated from the content process side, and there's not an easy and clean way to have the parent process send us the connection type after construction of the NeckoParent, other than have the NeckoChild request it either synchronously, or doing it async and hoping it's not asked for the value before the response comes in.) Differential Revision: https://phabricator.services.mozilla.com/D26232
d029091d7fd831b30cbc4a660c03f962b20fa44e: Bug 1540573 - P2. Have GeckoRuntime listen for network link changes when in the foreground. r=snorp
Chris Pearce <cpearce@mozilla.com> - Mon, 06 May 2019 22:41:10 +0000 - rev 472810
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1540573 - P2. Have GeckoRuntime listen for network link changes when in the foreground. r=snorp This allows Gecko to react to network link/status changes events as needed. Differential Revision: https://phabricator.services.mozilla.com/D28942
6a17951bc4b981f455e3b8f54db29b5ed28fa122: Bug 1540573 - P1. Observe ProcessLifecycle events in GeckoRuntime. r=snorp
Eugen Sawin <esawin@mozilla.com>, Chris Pearce <cpearce@mozilla.com> - Mon, 06 May 2019 22:40:56 +0000 - rev 472809
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1540573 - P1. Observe ProcessLifecycle events in GeckoRuntime. r=snorp This is esawin's patch from Bug 1544076; D28083. Differential Revision: https://phabricator.services.mozilla.com/D28941
bb4e78986eed98bb51eaa06e20e9ea032d62f3fe: Bug 1257565 - move addon blocklist tests from services/common to the blocklist dir, r=leplatrem
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 07 May 2019 00:56:01 +0000 - rev 472808
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1257565 - move addon blocklist tests from services/common to the blocklist dir, r=leplatrem Differential Revision: https://phabricator.services.mozilla.com/D29835
c4f071c9887145606f28db1e31a076f691777461: Bug 1257565 - add remote settings support for plugin and addon blocklist, r=aswan
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 07 May 2019 00:55:53 +0000 - rev 472807
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1257565 - add remote settings support for plugin and addon blocklist, r=aswan MozReview-Commit-ID: AiGycyhGUta Differential Revision: https://phabricator.services.mozilla.com/D29834
77ec8a41ee7361d9f02511b6992747857931485c: Bug 1257565 - switch gfx blocklist over to kinto-based storage, r=leplatrem,aswan
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 07 May 2019 00:55:32 +0000 - rev 472806
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1257565 - switch gfx blocklist over to kinto-based storage, r=leplatrem,aswan Differential Revision: https://phabricator.services.mozilla.com/D29833
f960290161ab3be6793e7eabc27d34573dea9a6e: Bug 1257565 - create a pref to phase out use of the XML blocklist, r=aswan
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 07 May 2019 00:55:15 +0000 - rev 472805
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1257565 - create a pref to phase out use of the XML blocklist, r=aswan Differential Revision: https://phabricator.services.mozilla.com/D29832
9ba2aa4a61437e0dd44dc8c5b48d3961b7b8ace1: Bug 1257565 - move blocklist tests to their own dir so we can easily keep them working and separate from tests for the new implementation, r=aswan
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 07 May 2019 00:55:02 +0000 - rev 472804
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1257565 - move blocklist tests to their own dir so we can easily keep them working and separate from tests for the new implementation, r=aswan Differential Revision: https://phabricator.services.mozilla.com/D29831
5268e93ef3483469953bf60e346af77b16687935: Bug 1052579 - Modify GTest for jemalloc_ptr_info() to check arenaId r=glandium
Chris Martin <cmartin@mozilla.com> - Tue, 07 May 2019 00:34:42 +0000 - rev 472803
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1052579 - Modify GTest for jemalloc_ptr_info() to check arenaId r=glandium In D25711, I added an arenaId member to `jemalloc_ptr_info_t` when `MOZ_DEBUG` is defined. This modifies the GTest for `jemalloc_ptr_info()` to ensure that the new member returns the correct value. Differential Revision: https://phabricator.services.mozilla.com/D30087
516cc2c504f5650083dddd563fa27c6a9cec615a: Bug 1548118 Part 3 - Always mark inner ColumnSetWrapper's children dirty before reflowing it if the outer ColumnSetWrapper is balancing. r=dbaron
Ting-Yu Lin <tlin@mozilla.com> - Mon, 06 May 2019 23:09:35 +0000 - rev 472802
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1548118 Part 3 - Always mark inner ColumnSetWrapper's children dirty before reflowing it if the outer ColumnSetWrapper is balancing. r=dbaron ColumnSetFrame always tries to reflow column content regardless of it's dirtiness. Making ColumnSetWrapperFrame's children dirty can have the same effect. Differential Revision: https://phabricator.services.mozilla.com/D29435
40a074be8bf08c2f8e3ca3da13ccad5328bac624: Bug 1548118 Part 2 - Extract computing column balancing depth logic to a function. r=dbaron
Ting-Yu Lin <tlin@mozilla.com> - Fri, 03 May 2019 19:25:57 +0000 - rev 472801
Push 35978 by shindli@mozilla.com at Tue, 07 May 2019 09:44:39 +0000
Bug 1548118 Part 2 - Extract computing column balancing depth logic to a function. r=dbaron Differential Revision: https://phabricator.services.mozilla.com/D29434
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip