02e1b59e669da81a15505dacd708e6fc7f567d5b: Bug 1523969 part 3 - Move method definition inline comments to new line in 'chrome/'. r=ehsan
Ryan Hunt <rhunt@eqrion.net> - Mon, 25 Feb 2019 16:04:01 -0600 - rev 461884
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1523969 part 3 - Move method definition inline comments to new line in 'chrome/'. r=ehsan Differential Revision: https://phabricator.services.mozilla.com/D21103
cf1a37a3c469b7c0e17c68d65c1e599f11d4172d: Bug 1523969 part 2 - Move method definition inline comments to new line in 'caps/'. r=bzbarsky
Ryan Hunt <rhunt@eqrion.net> - Mon, 25 Feb 2019 16:03:35 -0600 - rev 461883
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1523969 part 2 - Move method definition inline comments to new line in 'caps/'. r=bzbarsky Differential Revision: https://phabricator.services.mozilla.com/D21102
2eff89bd9d57460ecd0e4f74c29396958070734b: Bug 1523969 part 1 - Move method definition inline comments to new line in accessible/. r=jamie
Ryan Hunt <rhunt@eqrion.net> - Mon, 25 Feb 2019 16:02:26 -0600 - rev 461882
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1523969 part 1 - Move method definition inline comments to new line in accessible/. r=jamie Differential Revision: https://phabricator.services.mozilla.com/D21101
0bb343e7c6cc77a950065579d9fc31e0be4c3334: Bug 1519097 - Implement the Hashbang Grammar proposal in JavaScript to allow a '#!' line at the very start of a script/module to be treated as beginning a single-line comment. r=arai
Jeff Walden <jwalden@mit.edu> - Mon, 14 Jan 2019 23:01:14 -0500 - rev 461881
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1519097 - Implement the Hashbang Grammar proposal in JavaScript to allow a '#!' line at the very start of a script/module to be treated as beginning a single-line comment. r=arai
ac3671d0724b559483cad2aa0996c31db440772f: Bug 1531199 - Update the test262 import to latest. r=anba
Jeff Walden <jwalden@mit.edu> - Wed, 27 Feb 2019 17:24:16 -0800 - rev 461880
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1531199 - Update the test262 import to latest. r=anba
10df6785552dcb1aaac3dfbbd1b6fe099fee3437: Bug 1440038 - Use SharedRGBImage in MediaEngineTabVideoSource r=pehrsons
sotaro <sotaro.ikeda.g@gmail.com> - Fri, 01 Mar 2019 08:45:50 +0900 - rev 461879
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1440038 - Use SharedRGBImage in MediaEngineTabVideoSource r=pehrsons Differential Revision: https://phabricator.services.mozilla.com/D21177
c59e07cae80fcf325ff695b5e24e4aa823f034fd: Bug 1531027 - Add an explicit copy constructor to StackTrace. r=ehsan
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 28 Feb 2019 11:00:14 +1100 - rev 461878
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1531027 - Add an explicit copy constructor to StackTrace. r=ehsan This only copies the first `mLength` elements in `mPcs`. Differential Revision: https://phabricator.services.mozilla.com/D21488
75dd13876d89896a73a456d92fb0f3de4e3c72dc: Bug 1531029 - Fix incorrect `sizeof` expression. r=ehsan
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 28 Feb 2019 11:05:34 +1100 - rev 461877
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1531029 - Fix incorrect `sizeof` expression. r=ehsan This doesn't change behaviour because `sizeof(uintptr_t)` equals `sizeof(uintptr_t*)`, but it's good to make things more obviously correct. Differential Revision: https://phabricator.services.mozilla.com/D21487
a8fafeb134457ed0fd12e2d38dba3fc00eaf6cae: Bug 1530657. Remove webrender user data properties from frames first, then destory them. r=jrmuizel
Timothy Nikkel <tnikkel@gmail.com> - Thu, 28 Feb 2019 16:55:25 -0600 - rev 461876
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1530657. Remove webrender user data properties from frames first, then destory them. r=jrmuizel If we destroy at the same time as removal, then the destruction can destroy other objects which in turn might remove frame properties and mess up the frame property table. This should cover all ways the webrender user data can get deleted from a frame property. The nsIFrame::RemoveDisplayItemDataForDeletion bit doesn't seem necessary to fix the intermittent but I think it is still necessary.
9ce3a685bbcd0901128dab0c7261ae00dd209381: Bug 1528651 - Followup to fix a warning on release or beta. r=aklotz
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Sat, 23 Feb 2019 06:58:07 +0900 - rev 461875
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1528651 - Followup to fix a warning on release or beta. r=aklotz
535b72af7ed8161582fb3a84f88689639c177435: Bug 1524006 - Add a medium-high priority queue between high and normal, r=froydnj
Olli Pettay <Olli.Pettay@helsinki.fi> - Thu, 28 Feb 2019 22:38:53 +0200 - rev 461874
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1524006 - Add a medium-high priority queue between high and normal, r=froydnj
0507c090702b82431521119b5d6f9873d8e0486f: Bug 1525856 - Enable the disabled portions of browser_trackingUI_fingerprinters.js and browser_trackingUI_cryptominers.js now that we correctly deal with channels in the face of the content blocking allow list; r=johannh
Ehsan Akhgari <ehsan@mozilla.com> - Wed, 27 Feb 2019 15:36:42 -0500 - rev 461873
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1525856 - Enable the disabled portions of browser_trackingUI_fingerprinters.js and browser_trackingUI_cryptominers.js now that we correctly deal with channels in the face of the content blocking allow list; r=johannh Differential Revision: https://phabricator.services.mozilla.com/D21425
ca609968769496871058ab18a471b0c3be5c67ad: Bug 1525458 - Part 4: Add a test that verifies that when the top-level page is on the content blocking allow-list, we don't emit unexpected content blocking events inside the content blocking log; r=baku
Ehsan Akhgari <ehsan@mozilla.com> - Thu, 21 Feb 2019 16:57:28 -0500 - rev 461872
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1525458 - Part 4: Add a test that verifies that when the top-level page is on the content blocking allow-list, we don't emit unexpected content blocking events inside the content blocking log; r=baku Differential Revision: https://phabricator.services.mozilla.com/D20877
bfadbf643f32e259d45f8b5af88c0300dc17b68f: Bug 1525458 - Part 3: Work around bug 1529728 by disabling tracking annotations in flash blocking classifier tests; r=baku
Ehsan Akhgari <ehsan@mozilla.com> - Thu, 21 Feb 2019 16:34:49 -0500 - rev 461871
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1525458 - Part 3: Work around bug 1529728 by disabling tracking annotations in flash blocking classifier tests; r=baku Differential Revision: https://phabricator.services.mozilla.com/D20876
03f6a90e46bd71ce3f8827c4dfedba6abd509867: Bug 1525458 - Part 2: Update the anti-tracking tests to expect storage access right away when the top-level document is on the allow list and tracking cookies are being blocked per the cookie policy; r=baku
Ehsan Akhgari <ehsan@mozilla.com> - Thu, 21 Feb 2019 14:56:59 -0500 - rev 461870
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1525458 - Part 2: Update the anti-tracking tests to expect storage access right away when the top-level document is on the allow list and tracking cookies are being blocked per the cookie policy; r=baku Differential Revision: https://phabricator.services.mozilla.com/D20875
d32503125d279a4729ddd5f2e62dd9a1a2f04d65: Bug 1525458 - Part 1: Only emit the loaded events for various content blocking categories in the presence of an allow-list entry for the top-level document when content would have been blocked otherwise; r=baku,dimi
Ehsan Akhgari <ehsan@mozilla.com> - Tue, 26 Feb 2019 18:51:14 -0500 - rev 461869
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1525458 - Part 1: Only emit the loaded events for various content blocking categories in the presence of an allow-list entry for the top-level document when content would have been blocked otherwise; r=baku,dimi Previously the code here used to emit the loaded events for every resource examined by the URL Classifier Features (in other words, every third party resource). But we only need to emit the events in cases where without the presence of the allow-list we would have blocked the content. Differential Revision: https://phabricator.services.mozilla.com/D20874
08157bb630a6626773395db07862b7de3d43a3db: Merge mozilla-central to inbound. a=merge CLOSED TREE
Oana Pop Rus <opoprus@mozilla.com> - Fri, 01 Mar 2019 00:08:19 +0200 - rev 461868
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Merge mozilla-central to inbound. a=merge CLOSED TREE
b9f41b8dd43ce371409b8d1c2d0b1c133c7e45a7: Bug 1531282 - MozTree event handlers should be attached in connectedCallback() instead of constructor. r=bgrins
Magnus Melin <mkmelin+mozilla@iki.fi> - Thu, 28 Feb 2019 21:58:48 +0200 - rev 461867
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1531282 - MozTree event handlers should be attached in connectedCallback() instead of constructor. r=bgrins This patch moves adding the event handlers into MozTree.connectedCallback. This allows <tree onkeydown="...."> to function properly. The patch also folds all the 10 handlers for keydown into one, and handling the different cases in a switch.
798297c168c5aa3ef85e228268cc98c9fd088dab: Bug 1523750: Re-sign quitter extension for use in release builds. r=me
Kris Maglione <maglione.k@gmail.com> - Thu, 28 Feb 2019 12:57:13 -0800 - rev 461866
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1523750: Re-sign quitter extension for use in release builds. r=me
5b59b3bf72d880c4b3e05156ef329854075b24f8: Bug 1518863: Part 5 - More extension protocol handler cleanup. r=aswan
Kris Maglione <maglione.k@gmail.com> - Tue, 26 Feb 2019 21:09:40 -0800 - rev 461865
Push 35631 by rgurzau@mozilla.com at Fri, 01 Mar 2019 13:06:03 +0000
Bug 1518863: Part 5 - More extension protocol handler cleanup. r=aswan This is not strictly related to the rest of the patches, but it was annoying me while I wrote them. Differential Revision: https://phabricator.services.mozilla.com/D21450
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip