1ccc6b10d0ffe385284ca06c460211907a96f2c3: Bug 1343068 - Add the JNI generate files in the list of ignored elements r=mystor
Sylvestre Ledru <sledru@mozilla.com> - Mon, 27 Feb 2017 23:27:53 +0100 - rev 345098
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1343068 - Add the JNI generate files in the list of ignored elements r=mystor MozReview-Commit-ID: CcNVKLrUQW6
b3dd5dafe84d2bee97521abf4b3baa48609c398f: Bug 1314458: Only enable VP9 hardware decoding on nightly channel. r=kentuckyfriedtakahe
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 24 Feb 2017 10:17:40 +0100 - rev 345097
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1314458: Only enable VP9 hardware decoding on nightly channel. r=kentuckyfriedtakahe MozReview-Commit-ID: H3NkZ1ulEij
9a8b52d23f06c18699f34bd79205fc99c58a8a68: Bug 1341890 - Fix line endings for ContentPrefs.h. r=billm
Andrew McCreight <continuation@gmail.com> - Fri, 24 Feb 2017 10:23:53 -0800 - rev 345096
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1341890 - Fix line endings for ContentPrefs.h. r=billm Also fix the indentation of gInitPrefs. MozReview-Commit-ID: 1vNwCSxyTo
737092ef7a833c2bff42c16a872b0b21378384c4: Bug 1341887 - Add fuzzing.enabled to gInitPrefs in FUZZING builds. r=billm
Andrew McCreight <continuation@gmail.com> - Wed, 22 Feb 2017 14:16:30 -0800 - rev 345095
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1341887 - Add fuzzing.enabled to gInitPrefs in FUZZING builds. r=billm MozReview-Commit-ID: Faw7Vohw6Lm
9afe051a090cfb55a2dca1a541fea0a883ecf119: Bug 591822 - reftest to make sure images taller or wider than 32767 pixels will be rendered r=tnikkel
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Sun, 28 Aug 2016 00:39:52 +0900 - rev 345094
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 591822 - reftest to make sure images taller or wider than 32767 pixels will be rendered r=tnikkel MozReview-Commit-ID: Ev4GmwYyaNu
df65d15b648daef67f1a76987c21f4fe9b23bdb7: bug 1294580 - prevent end-entity certificates from being their own trust anchors r=Cykesiopka
David Keeler <dkeeler@mozilla.com> - Fri, 24 Feb 2017 12:32:41 -0800 - rev 345093
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
bug 1294580 - prevent end-entity certificates from being their own trust anchors r=Cykesiopka MozReview-Commit-ID: KaZaFG8AWwl
012f622e6db538ca428ebbd12a219b71c4275d16: servo: Merge #15568 - Fix #15513: Stop spacebar scrolling directly from the glutin window (from samgiles:15513-space-scroll); r=asajeffrey
Sam Giles <sam.e.giles@gmail.com> - Mon, 27 Feb 2017 12:54:26 -0800 - rev 345092
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
servo: Merge #15568 - Fix #15513: Stop spacebar scrolling directly from the glutin window (from samgiles:15513-space-scroll); r=asajeffrey This completely removes spacebar scrolling using the current method, fixing #15513. See #15513 for a discussion, as the _right thing to do_ is perhaps a UX problem - and perhaps worth a follow up. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix #15513. No tests for these changes yet, as I'm just kicking off a discussion about how this should work. Source-Repo: https://github.com/servo/servo Source-Revision: eb8d0c3df89e3f51c2610014ab3289eb552f95c9
1505329bcea631ff32c8f278a324a7165fb8de0f: Merge m-c to autoland, a=merge
Wes Kocher <wkocher@mozilla.com> - Mon, 27 Feb 2017 13:39:07 -0800 - rev 345091
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Merge m-c to autoland, a=merge MozReview-Commit-ID: 8dvpEkAL5Vh
62736acb85d02f7fe6e8135a46646b7fa0e4703b: Bug 1340620 - Use inverted loading icons with Compact Theme. r=Gijs
J. Ryan Stinnett <jryans@gmail.com> - Mon, 27 Feb 2017 13:55:59 -0600 - rev 345090
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1340620 - Use inverted loading icons with Compact Theme. r=Gijs For selected tabs, the Compact Themes use bright blue tab background colors, which makes the blue loading icon hard to see. For this state, use a white loading icon instead. MozReview-Commit-ID: 5P2VWgR4Iue
68763bfa6d054cd6bc63b61c3d127e721d8aaec8: Bug 1338215 - use a windowless browser for thumbnail hosting, r=markh
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Mon, 27 Feb 2017 19:58:55 +0000 - rev 345089
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1338215 - use a windowless browser for thumbnail hosting, r=markh MozReview-Commit-ID: LWzMDHu0N8H
01bc4c9ad3b50d29b61e0bbfbba2862af8cf5b81: Bug 1342162 - Align pageLoad key with WebDriver; r=maja_zf
Andreas Tolfsen <ato@mozilla.com> - Thu, 23 Feb 2017 18:33:26 +0000 - rev 345088
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1342162 - Align pageLoad key with WebDriver; r=maja_zf The WebDriver specification recently decided to use "pageLoad" instead of "page load" to identify the page load duration timeout in the session timeouts configuration object: https://github.com/w3c/webdriver/pull/796 This change aligns Marionette with WebDriver, and as long as this patch is uplifted to Aurora (53) and Beta (52) in reasonable time, we should be able to avoid the backwards compatibility dance with the Python client (for upgrade tests) because the original change to the data format landed on the current Firefox version: https://bugzilla.mozilla.org/show_bug.cgi?id=1316622 MozReview-Commit-ID: BzQeJku4AFS
3e542f18ed6278e1285cae899453679841ea5296: Bug 1337940 - Part 3 - Restrict the amount of session history we keep around during test_parse_rule. r=dbaron
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 22 Feb 2017 22:44:49 +0100 - rev 345087
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1337940 - Part 3 - Restrict the amount of session history we keep around during test_parse_rule. r=dbaron During its run this test amasses a considerable collection of session history. Because the page title never changes, though, the Android session store previously never attempted to capture the state here. As of this bug this has changed and history change events now (correctly) trigger a session store data update on Android as well. On a debug build running on the Android emulator however, collecting the session history data can take up to 1 s when the session history count approaches the default "browser.sessionhistory.max_entries" limit of 50 entries, which increases the total running time of this test considerably and leads to timeouts (although only just). Bug 1341810 will track possibly improving the session store performance on Android by not doing a full history collect when not needed, but for the time being, restricting the amount of session history we keep around during this test is the simpler solution. MozReview-Commit-ID: JRREidiWnM3
6fa30faf379173a45cda1c400a15e4849b94013a: Bug 1337940 - Part 2 - Make session store form data test work again. r=ahunt
Jan Henning <jh+bugzilla@buttercookie.de> - Mon, 13 Feb 2017 22:16:36 +0100 - rev 345086
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1337940 - Part 2 - Make session store form data test work again. r=ahunt Collecting data for history changes causes an additional session store data update for that tab when navigating back, which needs to be accounted for in this test. Therefore we now also wait for DOMTitleChanged before assuming that the tab has navigated to its intended location. MozReview-Commit-ID: FDNQednXPWh
4285ead0e57a8372d81dd76cf5a4182c3bd3e1fb: Bug 1337940 - Part 1 - Capture session store tab data on history listener notifications. r=ahunt
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 11 Feb 2017 21:07:29 +0100 - rev 345085
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1337940 - Part 1 - Capture session store tab data on history listener notifications. r=ahunt So far we've simply used DOMTitleChanged as a proxy for navigation, since it's the earliest opportunity at which we have all necessary data for a new history entry (session history itself as well as tab URL and *title*) available. However it turns out that this is not 100 % reliable, since some pages might e.g. implement their navigation in JS using the history API, which won't necessarily trigger any DOMTitleChanged events. In those case we'd fail to update the tab's session history in the session store unless the user eventually navigated to someplace else that actually triggers a title change event again - if the browser was closed before that, we'd fail to properly restore the user's state. To fix this, we take a similar approach as the desktop session store and collect a tab's history data again when receiving any history change notification for that tab. Because the OnHistory... notifications are mostly cancellable, the session history hasn't been actually updated yet at the point the history listener is being called. We therefore can't synchronously call onTabLoad() from within our history change notification handler and have to schedule an async timeout instead so as to give the session history a chance to complete updating its state. MozReview-Commit-ID: LgHer940QwT
f30e28369136fcb28dddcd55a94d98e2816009e9: Backed out changeset 84a017610f03 (bug 1342427) for browser_applications_selection.js failures a=backout
Wes Kocher <wkocher@mozilla.com> - Mon, 27 Feb 2017 11:55:36 -0800 - rev 345084
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Backed out changeset 84a017610f03 (bug 1342427) for browser_applications_selection.js failures a=backout MozReview-Commit-ID: KkzcQPJgLex
370364bfc2b5a266e67b63fab5eb9f800220601b: Bug 1338997 - Ensure that the transformation matrices are invertible r=mattwoodrow
Miko Mynttinen <mikokm@gmail.com> - Thu, 23 Feb 2017 20:42:10 +0100 - rev 345083
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1338997 - Ensure that the transformation matrices are invertible r=mattwoodrow MozReview-Commit-ID: A5nHNcnkrNN
c2fbddc3469aeb1e47c33f37eeeea8352c01afd7: Bug 1331139 - Sync safebrowsing.proto from Chromium. r=francois
Thomas Nguyen <tnguyen@mozilla.com> - Mon, 27 Feb 2017 12:18:50 +0800 - rev 345082
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1331139 - Sync safebrowsing.proto from Chromium. r=francois MozReview-Commit-ID: KWi8wWhqCcr
2bd28e8cf65f33cb52cd2ab46172669433339a7e: Bug 1331139 - Enable download protection for V4 lists. r=francois
Thomas Nguyen <tnguyen@mozilla.com> - Mon, 27 Feb 2017 12:18:33 +0800 - rev 345081
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1331139 - Enable download protection for V4 lists. r=francois MozReview-Commit-ID: 8IHKGvXQjPt
9bec0be69329be127194c60ff6986efa549c35bc: Bug 1341097 - part 4: misc. small optimizations, r=mak
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Mon, 20 Feb 2017 16:06:27 +0000 - rev 345080
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1341097 - part 4: misc. small optimizations, r=mak The MigrationUtils change is because 99% of the time we will only have 1 visit per URI, and so we spend silly amounts of time doing nothing. Time spent in composing our undo structure went from ~800ms to ~550ms with this change. The other change just seemed obvious - when visits aren't recent, we shouldn't add them to 'recently visited' lists, which seem to use 'time this function was called' as the time associated with an entry, which is incorrect. MozReview-Commit-ID: 2I0D5ApOCI7
0ad0959be648cd9533167931a7ce4901050c0218: Bug 1341097 - part 3: don't dispatch oodles of titlechanged notifications for new history entries, r=mak
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Mon, 27 Feb 2017 18:26:21 +0000 - rev 345079
Push 31431 by cbook@mozilla.com at Tue, 28 Feb 2017 10:23:16 +0000
Bug 1341097 - part 3: don't dispatch oodles of titlechanged notifications for new history entries, r=mak MozReview-Commit-ID: 7jHOcCQ5ZBb
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip