ddcfa0a1fa00353cb74f5b237a9652bce8398b45: Bug 1593170. Adjust how we deal with the reftest events for async plugin drawing for the fission changes to the reftest harness. r=mattwoodrow
Timothy Nikkel <tnikkel@gmail.com> - Mon, 18 Nov 2019 11:26:33 +0000 - rev 502489
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1593170. Adjust how we deal with the reftest events for async plugin drawing for the fission changes to the reftest harness. r=mattwoodrow The long code comment explains. Differential Revision: https://phabricator.services.mozilla.com/D51345
449d87c4759340bd61e4ae3ab0bc67f826ac02cf: Bug 1593170. Make the reftest harness deal with SynchronizeForSnapshot and FlushRendering returning promises. r=mattwoodrow
Timothy Nikkel <tnikkel@gmail.com> - Mon, 18 Nov 2019 11:26:20 +0000 - rev 502488
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1593170. Make the reftest harness deal with SynchronizeForSnapshot and FlushRendering returning promises. r=mattwoodrow The code comment mostly explains the design. Basically, we force nothing to happen while we wait for the promises to finish and instead record what we need to do once the promise is finished, and do those pending tasks when it's finished. Differential Revision: https://phabricator.services.mozilla.com/D51344
06f14f474f284543abd637543cecfa4d6079be50: Bug 1593170. Make the reftest-content.js functions FlushRendering and SynchronizeForSnapshot work on Fission child oop iframes. r=mattwoodrow,kmag
Timothy Nikkel <tnikkel@gmail.com> - Mon, 18 Nov 2019 11:25:11 +0000 - rev 502487
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1593170. Make the reftest-content.js functions FlushRendering and SynchronizeForSnapshot work on Fission child oop iframes. r=mattwoodrow,kmag This changes them to return a promise that resolves when the work is done, but we still need to change the callers to handle this new return type and do the right thing when these functions do their work async-ly. To do this we add a JSWindowActor called ReftestFission. reftest-content.js communicates with this actor via reftest.jsm. Differential Revision: https://phabricator.services.mozilla.com/D51343
561598bb2f394a1301650aa606df06cb310cdaac: Bug 1597038 - Fix crash in Cursor::SendResponseInternal with nsresult response type and non-empty files. r=dom-workers-and-storage-reviewers,ttung
Simon Giesecke <sgiesecke@mozilla.com> - Mon, 18 Nov 2019 17:37:31 +0000 - rev 502486
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1597038 - Fix crash in Cursor::SendResponseInternal with nsresult response type and non-empty files. r=dom-workers-and-storage-reviewers,ttung Differential Revision: https://phabricator.services.mozilla.com/D53393
9f82401f147b1c20e45ec757ed2e6221a720e88d: Bug 1596609 - Make more tests reuse Fission content processes. r=kmag
Andrew McCreight <continuation@gmail.com> - Mon, 18 Nov 2019 21:55:08 +0000 - rev 502485
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596609 - Make more tests reuse Fission content processes. r=kmag These tests are frequently leaking a single BackstagePass and its XPCWN. To paper over the leak, this patch makes us reuse Fission content processes in a few places. I filed bug 1596611 about fixing the leak and reverting the change. Differential Revision: https://phabricator.services.mozilla.com/D53108
635be62762b9f8fa94f3cb38e81d356a6b8f22bb: Bug 1596953 - Add valgrind to android-build image. r=froydnj
Jesse Schwartzentruber <truber@mozilla.com> - Mon, 18 Nov 2019 20:38:11 +0000 - rev 502484
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596953 - Add valgrind to android-build image. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D53287
582c1acfb3483e087316793a965497b9dfdbc208: Bug 1564873 - Stop using mem::uninitialized to pass memory to the GPU. r=Gankro
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 18 Nov 2019 21:40:39 +0000 - rev 502483
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1564873 - Stop using mem::uninitialized to pass memory to the GPU. r=Gankro Use Vec::reserve + as_ptr, then raw pointers. Alternative is to require T: Default, and then push T::default() or something. Differential Revision: https://phabricator.services.mozilla.com/D53360
7f64e4879257aefc6450321a66532576ca29079b: Bug 1597129 - fix newline usage for manifest writing in mach addtest, r=ahal
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Mon, 18 Nov 2019 21:12:22 +0000 - rev 502482
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1597129 - fix newline usage for manifest writing in mach addtest, r=ahal Differential Revision: https://phabricator.services.mozilla.com/D53353
93c199bb39288eb84cec5d26723a400263000f59: Bug 1594925 - Follow up on the doc documentation r=ahal
Sylvestre Ledru <sledru@mozilla.com> - Mon, 18 Nov 2019 21:12:51 +0000 - rev 502481
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1594925 - Follow up on the doc documentation r=ahal Differential Revision: https://phabricator.services.mozilla.com/D53395
859e84396f6dc4584bbb0d53be2756c26ca78ea0: Bug 1595093 - Make sure we always have a valid software backend, regardless of what prefs the user sets. r=lsalzman
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 18 Nov 2019 21:15:58 +0000 - rev 502480
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1595093 - Make sure we always have a valid software backend, regardless of what prefs the user sets. r=lsalzman Differential Revision: https://phabricator.services.mozilla.com/D53718
765b9da8b818804ee68c8e18f92d2bdaa1794d8e: Backed out 2 changesets (bug 1405971) on evilpies's request
Bogdan Tara <btara@mozilla.com> - Mon, 18 Nov 2019 23:08:21 +0200 - rev 502479
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Backed out 2 changesets (bug 1405971) on evilpies's request Backed out changeset dd473ab6821e (bug 1405971) Backed out changeset 3b42f1a5097a (bug 1405971)
21f755c04005255c5305a13ad9087420e4489b7b: Bug 1580246: Remove object-literal singleton objects allocated at parse. r=mgaudet,jandem
Chris Fallin <cfallin@mozilla.com> - Mon, 18 Nov 2019 20:57:50 +0000 - rev 502478
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1580246: Remove object-literal singleton objects allocated at parse. r=mgaudet,jandem Instead, this patch introduces a new `ObjLiteral` mini-bytecode format that is used to carry object-literal information from parse time to a later time at which GC objects are safe to allocate. The mini-bytecode simply specifies a list of fields and constant field values. The original intent of this patch (realized in previous versions of it) was to make this an opcode, and completely replace object creation sequences (NEWINIT, INITPROP, INITPROP, ...) with one OBJLITERAL opcode. However, there are quite a few performance regressions that occur when replacing the finely-tuned set of optimizations around this with a new mechanism. As a result, this patch only defers allocation of the objects until the very end of parse. Each object literal adds an ObjLiteralCreationData instance to the GC-things list, and when the GC-things list is processed to perform deferred allocations, the described objects will be created. This is a rebased version of the original patch (landed as D47985 and then backed out) with the Kraken regression (bug 1594753) fixed as noted in the bug above. Differential Revision: https://phabricator.services.mozilla.com/D52383
91697065e99f5b88ceaaf92af99ebdbbfc1dda88: Bug 1589476 - Emit a separate notification when a tracker from the Level 2 Disconnect blocklist is observed on a page and use this code to avoid using the URL classifer service in the front-end; r=nhnt11,droeh
Ehsan Akhgari <ehsan@mozilla.com> - Mon, 18 Nov 2019 20:56:36 +0000 - rev 502477
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1589476 - Emit a separate notification when a tracker from the Level 2 Disconnect blocklist is observed on a page and use this code to avoid using the URL classifer service in the front-end; r=nhnt11,droeh Differential Revision: https://phabricator.services.mozilla.com/D49660
ba115d212e18bad5168af1ae0541c44de1a20089: Bug 1596800 - Remove document.getAnonymousNodes as well. r=smaug
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 18 Nov 2019 19:15:16 +0000 - rev 502476
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596800 - Remove document.getAnonymousNodes as well. r=smaug As it always returns null. Depends on D53342 Differential Revision: https://phabricator.services.mozilla.com/D53343
26d109ef85da49b7f113e65c61908dbb5d7ea846: Bug 1596800 - Remove document.getBindingParent. r=smaug
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 18 Nov 2019 19:06:51 +0000 - rev 502475
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596800 - Remove document.getBindingParent. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D53342
d5db2146b9c5519a2d42233c4699818ba347ec2a: Bug 1596800 - Remove document.getBindingParent usage from autocomplete-popup. r=mconley
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 18 Nov 2019 19:06:51 +0000 - rev 502474
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596800 - Remove document.getBindingParent usage from autocomplete-popup. r=mconley This preserves the behavior, though I think we could probably remove that block altogether? Depends on D53340 Differential Revision: https://phabricator.services.mozilla.com/D53341
c2817cb864536cf73287225833f89c0619209ac6: Bug 1596800 - Remove document.getBindingParent usage from devtools. r=jdescottes
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 18 Nov 2019 20:54:10 +0000 - rev 502473
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596800 - Remove document.getBindingParent usage from devtools. r=jdescottes This removes the concept of shadowAnonymous, which doesn't make a lot of sense, and re-enables the shadow dom tests which were disabled when we removed the old style system (as stylo didn't supported shadow DOM yet by then). This is a change in behavior as you can now remove nodes from shadow DOM (no reason you weren't able to, before). Differential Revision: https://phabricator.services.mozilla.com/D53340
cceae677e859c9915d895bee2783ca1c0c34a296: Bug 1596800 - Remove document.getBindingParent usage from preferences search. r=mconley
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 18 Nov 2019 19:07:47 +0000 - rev 502472
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596800 - Remove document.getBindingParent usage from preferences search. r=mconley When the focus moves elsewhere inside the <tree> blur events aren't dispatched outside the shadow tree (as expected), so checking the originalTarget is always bogus. Furthermore, the event handler does nothing if the input isn't focused, and when the input is blurred the tree takes care of calling stopEditing itself, so this change should be pretty safe in general: https://searchfox.org/mozilla-central/rev/492214c05cde6e6db5feff9465ece4920400acc3/toolkit/content/widgets/tree.js#1083 It's not clear to me whether the blur event handler is doing anything at all after bug 1547382 (before this patch), as the binding parent is not a <xul:textbox> anymore, so <input>.getBindingParent() will return the <tree>... Depends on D53338 Differential Revision: https://phabricator.services.mozilla.com/D53339
5bc4fbe48df7276c4b6da448e9b85953620ac913: Bug 1596800 - Remove document.getBindingParent usage from PluginChild.jsm. r=mconley
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 18 Nov 2019 19:06:50 +0000 - rev 502471
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596800 - Remove document.getBindingParent usage from PluginChild.jsm. r=mconley It wants to get the containing shadow host of the target to get to the plugin. Do that explicitly. Depends on D53337 Differential Revision: https://phabricator.services.mozilla.com/D53338
85408aaba4a32de2ecf495093f24643e93154292: Bug 1596800 - Remove unneeded forced layout flush in PluginChild.jsm. r=mconley
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 18 Nov 2019 19:06:50 +0000 - rev 502470
Push 114172 by dluca@mozilla.com at Tue, 19 Nov 2019 11:31:10 +0000
Bug 1596800 - Remove unneeded forced layout flush in PluginChild.jsm. r=mconley We don't need layout flushes to attach XBL bindings anymore, as there are no XBL bindings. This is drive-by. Depends on D53336 Differential Revision: https://phabricator.services.mozilla.com/D53337
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 tip