fd8e8a3cbfacf64f6eae71ef13524db194c8c8ec: Bug 1522705 - Add streaming response support to GeckoWebExecutor r=esawin,agi
James Willcox <snorp@snorp.net> - Fri, 22 Feb 2019 21:46:05 +0000 - rev 460661
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1522705 - Add streaming response support to GeckoWebExecutor r=esawin,agi Differential Revision: https://phabricator.services.mozilla.com/D19504
69196a59302d12241df753ed581f899e0e0ba217: Bug 1522705 - Add /data/<count> path to HttpBinHandler r=geckoview-reviewers,esawin
James Willcox <snorp@snorp.net> - Fri, 22 Feb 2019 21:45:57 +0000 - rev 460660
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1522705 - Add /data/<count> path to HttpBinHandler r=geckoview-reviewers,esawin This simply lets you request 'count' random bytes. A SHA-256 digest is included for verifying the integrity of the response. Differential Revision: https://phabricator.services.mozilla.com/D19503
e657fe2ca2a3d8fe935d3ea7308938b40f94a17c: Bug 1528146. Fix how web extensions are injected into about:blank. r=kmag
Boris Zbarsky <bzbarsky@mit.edu> - Fri, 22 Feb 2019 21:27:44 +0000 - rev 460659
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1528146. Fix how web extensions are injected into about:blank. r=kmag The basic idea is to make non-initial about:blank fire document-element-inserted notifications just like every other document. We then ensure that there's a notification (initial-document-element-inserted) that only gets fired once per window for documents that are in a window. This notification is what webextensions use to inject into the document. The old setup which injected into about:blank when its global is created gets removed in favor of injecting the same way as into every other document. The changes to Document.cpp are fixing a bug in the "block the parser" stuff webextensions do. For about:blank, the blocking happens at a point when the parser really has nothing else to parse (since it's parsing the empty string). So the blocking is a no-op. But we do want to prevent DOMContentLoaded firing, because otherwise the "end of document" scripts could run before we finish doing the "beginning of document" work in webextensions. So we want to make sure we block DOMContentLoaded, not just the load event. Differential Revision: https://phabricator.services.mozilla.com/D19892
1033b5aecacc6e1ceae8a30639ff7b20cd322479: Bug 1528762. Don't inject customElements.js into system-principal about:blank. r=bgrins
Boris Zbarsky <bzbarsky@mit.edu> - Fri, 22 Feb 2019 21:32:09 +0000 - rev 460658
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1528762. Don't inject customElements.js into system-principal about:blank. r=bgrins Otherwise we get a performance regression on tp5o responsiveness and tp5o_webext responsiveness when about:blank starts firing document-element-inserted notifications. Differential Revision: https://phabricator.services.mozilla.com/D20873
4978133d62260c9405d07d049e01bda746dee9af: Backed out changeset e89b6e3d3de8 (bug 1520163) for profile-guided optimization builds bustage CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Fri, 22 Feb 2019 23:27:42 +0200 - rev 460657
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Backed out changeset e89b6e3d3de8 (bug 1520163) for profile-guided optimization builds bustage CLOSED TREE
901be6adcc2d3d3e24b1a2d70213cd12565e977e: Bug 1529427 - Refactor sources reducer so that all source actors are included.
Jason Laster <jlaster@mozilla.com> - Fri, 22 Feb 2019 20:37:42 +0000 - rev 460656
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1529427 - Refactor sources reducer so that all source actors are included. Differential Revision: https://phabricator.services.mozilla.com/D20592
d945b5bd54f03d378481a960ae8293f6ce375aeb: Bug 1527151 - Reset securityUI.contentBlockingEvent on top level location changes. r=Ehsan
Johann Hofmann <jhofmann@mozilla.com> - Fri, 22 Feb 2019 19:44:03 +0000 - rev 460655
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1527151 - Reset securityUI.contentBlockingEvent on top level location changes. r=Ehsan We had previously missed to call browser.updateSecurityUIForContentBlockingEvent on onLocationChange updates, to reset the contentBlockingEvent state. This would mean that on tab switch the contentBlockingEvent state for benign pages would still be what it was set to on the last tracker page. Differential Revision: https://phabricator.services.mozilla.com/D20328
cf7f4cea93be4a11ecb91c916a0514e403edd042: Bug 1528396 - More precise GL symbol loading. r=lsalzman
Jeff Gilbert <jgilbert@mozilla.com> - Fri, 22 Feb 2019 21:17:28 +0000 - rev 460654
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1528396 - More precise GL symbol loading. r=lsalzman In particular, don't fallback to loading symbols from any loaded library. Differential Revision: https://phabricator.services.mozilla.com/D20455
fd3f6a36c79f737eb54b77e11bf87729286257f1: Bug 1523631 - Part 5: Avoid GCC warning when including dictionary types in WebIDL, r=bzbarsky
Nika Layzell <nika@thelayzells.com> - Fri, 22 Feb 2019 15:48:44 +0000 - rev 460653
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1523631 - Part 5: Avoid GCC warning when including dictionary types in WebIDL, r=bzbarsky This warning (as an error) is showing up with this patch due to the new use of AddEventListenerOptions in ChromeUtilsBinding.h. That header is included in some codegen units which have this warning enabled, which revealed the issue. I believe the warning is spurious in this case, but fixing it doesn't seem like a big deal. Requesting review from Boris, as he added the comment 6 years ago. Depends on D20015 Differential Revision: https://phabricator.services.mozilla.com/D20824
a3f79e3f59f9795820d10c734e247c06326e3637: Bug 1523631 - Part 4: Add tests for event listeners on JS Window Actor Protocols, r=jdai
Nika Layzell <nika@thelayzells.com> - Fri, 22 Feb 2019 15:17:03 +0000 - rev 460652
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1523631 - Part 4: Add tests for event listeners on JS Window Actor Protocols, r=jdai Depends on D20014 Differential Revision: https://phabricator.services.mozilla.com/D20015
20be5e162a7d1e33056ef99e2dd858eaad97f61e: Bug 1523631 - Part 3: Unregister in content processes as well, r=jdai
Nika Layzell <nika@thelayzells.com> - Fri, 22 Feb 2019 15:17:01 +0000 - rev 460651
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1523631 - Part 3: Unregister in content processes as well, r=jdai Depends on D20013 Differential Revision: https://phabricator.services.mozilla.com/D20014
3575c9a372e76640a3a6fe1e3854b74ac2188d9b: Bug 1523631 - Part 2: Add support for event listeners to JS Window Actor Protocols, r=jdai,qdot
Nika Layzell <nika@thelayzells.com> - Fri, 22 Feb 2019 19:28:50 +0000 - rev 460650
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1523631 - Part 2: Add support for event listeners to JS Window Actor Protocols, r=jdai,qdot This patch takes the approach of keeping track of a list of nsWindowRoot objects in the JSWindowActorService. Listeners are then maintained for each type of actor for every nsWindowRoot. Depends on D20012 Differential Revision: https://phabricator.services.mozilla.com/D20013
2beb789b521f78a7ecf8ae6f4138c7b14393e8aa: Bug 1523631 - Part 1: Add a JSWindowActorProtocol object for protocol-specific state, r=jdai
Nika Layzell <nika@thelayzells.com> - Fri, 22 Feb 2019 15:16:51 +0000 - rev 460649
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1523631 - Part 1: Add a JSWindowActorProtocol object for protocol-specific state, r=jdai Differential Revision: https://phabricator.services.mozilla.com/D20012
e89b6e3d3de81c918b6fb6ed334a642d1f46bef2: Bug 1520163 - Add linux64-nasm toolchain. r=glandium
Thomas Daede <tdaede@mozilla.com> - Fri, 22 Feb 2019 20:41:20 +0000 - rev 460648
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1520163 - Add linux64-nasm toolchain. r=glandium Differential Revision: https://phabricator.services.mozilla.com/D20037
696c4b4978addce673d53097f377140ee140f964: Bug 1527767 - Make all JS allocator functions accept an arena as an argument r=sfink
Chris Martin <cmartin@mozilla.com> - Fri, 22 Feb 2019 18:12:05 +0000 - rev 460647
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1527767 - Make all JS allocator functions accept an arena as an argument r=sfink Currently, some of the JS allocators accept an 'arena' argument, but some don't. This change makes it so they all do. This is nice for consistency, but it also feeds into Bug 1052579, which will need to use arenas for JSString backing buffers. Differential Revision: https://phabricator.services.mozilla.com/D19717
218e965ee9b363861ff07772f24c23aed3ac3d37: Bug 1129354 - Implement draft extension OES_fbo_render_mipmap. r=lsalzman,qdot
Jeff Gilbert <jgilbert@mozilla.com> - Fri, 22 Feb 2019 19:25:20 +0000 - rev 460646
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1129354 - Implement draft extension OES_fbo_render_mipmap. r=lsalzman,qdot Differential Revision: https://phabricator.services.mozilla.com/D20397
62bec7b76cab37d9678759b7b2d5be5eb1e86e69: Bug 1525035 - Handle IME composition in Quantum Bar. r=adw
Marco Bonardo <mbonardo@mozilla.com> - Fri, 22 Feb 2019 20:02:35 +0000 - rev 460645
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1525035 - Handle IME composition in Quantum Bar. r=adw Differential Revision: https://phabricator.services.mozilla.com/D20826
ca2b32dbbae0129a998e50f9199fc822376163d1: Backed out changeset ac316114822b (bug 1527782) for perma failing browser_all_files_referenced.js CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Fri, 22 Feb 2019 21:42:48 +0200 - rev 460644
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Backed out changeset ac316114822b (bug 1527782) for perma failing browser_all_files_referenced.js CLOSED TREE
b892c1e3909ffee9cb1c39c45c12db7e7c9b757a: Bug 1520523 - Update Raptor Chromium rev; r=davehunt
Rob Wood <rwood@mozilla.com> - Fri, 22 Feb 2019 19:31:52 +0000 - rev 460643
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1520523 - Update Raptor Chromium rev; r=davehunt Differential Revision: https://phabricator.services.mozilla.com/D20814
244cd329c3bbb03ca23cc24ea1468225a306bc9c: Bug 1529707: Use RelativeLuminanceUtils::Compute() to test for dark GTK themes (ignoring alpha channel). r=karlt
Daniel Holbert <dholbert@cs.stanford.edu> - Fri, 22 Feb 2019 19:32:14 +0000 - rev 460642
Push 35596 by rmaries@mozilla.com at Sat, 23 Feb 2019 04:13:22 +0000
Bug 1529707: Use RelativeLuminanceUtils::Compute() to test for dark GTK themes (ignoring alpha channel). r=karlt Previously we were using NS_GetLuminosity which asserts for non-opaque colors, and my system theme happens to use a background color with alpha=0.999. Luminosity judgements do get a bit more hand-wavy as colors get more transparent, but it seems like we can still reasonably make an overall "dark theme" judgement based on the RGB channels. Differential Revision: https://phabricator.services.mozilla.com/D20748
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip