50ef519acb974b747e4d1c1683907cf287f7d758: Bug 1462703 - Upgrade the created element after callback runs
draft
Timothy Guan-tin Chien <timdream@gmail.com> - Wed, 23 May 2018 13:04:18 +0800 - rev 798625
Push
110807 by timdream@gmail.com at Wed, 23 May 2018 07:07:45 +0000
Bug 1462703 - Upgrade the created element after callback runs
nsContentUtils::NS_NewXULOrHTMLElement will call into
CustomElementRegisty::RegisterCallbackUpgradeElement, which keeps
the newly created element, allowing RunCustomElementCreationCallback
to upgrade them after the callback runs.
It is unclear if this changes the order of constructor executions,
but even so it should not affact our use case.
MozReview-Commit-ID: LWTn7B35aBv
705689bc49b044a0bbed2527550e701cb8b42740: Bug 1462703 - Set returned CustomElementDefinition again after script runner is set
draft
Timothy Guan-tin Chien <timdream@gmail.com> - Tue, 22 May 2018 07:30:07 +0800 - rev 798624
Push
110807 by timdream@gmail.com at Wed, 23 May 2018 07:07:45 +0000
Bug 1462703 - Set returned CustomElementDefinition again after script runner is set
This would help in the case where it is safe to run script in-place and
the CustomElementDefinition is available before the function exits.
This fixes the tests changed.
MozReview-Commit-ID: Ays91W94WZm
c142c5c69a04c86f192526f8324a0278cbb721ba: Bug 1462703 - Additional setElementCreationCallback tests in XUL document
draft
Timothy Guan-tin Chien <timdream@gmail.com> - Wed, 23 May 2018 14:13:22 +0800 - rev 798623
Push
110806 by timdream@gmail.com at Wed, 23 May 2018 07:00:41 +0000
Bug 1462703 - Additional setElementCreationCallback tests in XUL document
These tests ensures the feature interacts well with our setup in XUL.
They work when
bug 1460815 was implemented so they sits in its own changeset.
MozReview-Commit-ID: Ia08tAewZyN
47058a61951c2974514e41e316e5370cfa4f9d8b: Bug 1462703 - Upgrade the created element after callback runs
draft
Timothy Guan-tin Chien <timdream@gmail.com> - Wed, 23 May 2018 13:04:18 +0800 - rev 798622
Push
110806 by timdream@gmail.com at Wed, 23 May 2018 07:00:41 +0000
Bug 1462703 - Upgrade the created element after callback runs
nsContentUtils::NS_NewXULOrHTMLElement will call into
CustomElementRegisty::RegisterCallbackUpgradeElement, which keeps
the newly created element, allowing RunCustomElementCreationCallback
to upgrade them after the callback runs.
It is unclear if this changes the order of constructor executions,
but even so it should not affact our use case.
MozReview-Commit-ID: LWTn7B35aBv
c77c8b995cbc3b0242d2644e41360d1e97688d24: Bug 1462703 - Additional setElementCreationCallback tests in XUL document
draft
Timothy Guan-tin Chien <timdream@gmail.com> - Wed, 23 May 2018 14:13:22 +0800 - rev 798621
Push
110805 by timdream@gmail.com at Wed, 23 May 2018 06:50:36 +0000
Bug 1462703 - Additional setElementCreationCallback tests in XUL document
These tests ensures the feature interacts well with our setup in XUL.
They work when
bug 1460815 was implemented so they sits in its own changeset.
MozReview-Commit-ID: Ia08tAewZyN
255f25a42e1b15916d23f7e9df170fc9b435030d: Bug 1462703 - Upgrade the created element after callback runs
draft
Timothy Guan-tin Chien <timdream@gmail.com> - Wed, 23 May 2018 13:04:18 +0800 - rev 798620
Push
110805 by timdream@gmail.com at Wed, 23 May 2018 06:50:36 +0000
Bug 1462703 - Upgrade the created element after callback runs
nsContentUtils::NS_NewXULOrHTMLElement will call into
CustomElementRegisty::RegisterCallbackUpgradeElement, which keeps
the newly created element, allowing RunCustomElementCreationCallback
to upgrade them after the callback runs.
It is unclear if this changes the order of constructor executions,
but even so it should not affact our use case.
MozReview-Commit-ID: LWTn7B35aBv
47c62a1e2f268e1be24c3fddfc006c3ad45ba4ac: Bug 1462703 - Set returned CustomElementDefinition again after script runner is set
draft
Timothy Guan-tin Chien <timdream@gmail.com> - Tue, 22 May 2018 07:30:07 +0800 - rev 798619
Push
110805 by timdream@gmail.com at Wed, 23 May 2018 06:50:36 +0000
Bug 1462703 - Set returned CustomElementDefinition again after script runner is set
This would help in the case where it is safe to run script in-place and
the CustomElementDefinition is available before the function exits.
This fixes the tests changed.
MozReview-Commit-ID: Ays91W94WZm
442444b5482a75a5750eb2a86f3621ade0680db2: Bug 1463555 - Queue adding the tabs to the inspector sidebar. r=Honza
draft
Gabriel Luong <gabriel.luong@gmail.com> - Wed, 23 May 2018 02:16:11 -0400 - rev 798618
Push
110804 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:18:04 +0000
Bug 1463555 - Queue adding the tabs to the inspector sidebar. r=Honza
MozReview-Commit-ID: EDr73JomKoZ
52bfc320649589a04634a9054a7fbb9ab3b5a7d9: Bug 1463652 - Lazy load the sourceMapURLService from the rule editor. r=pbro
draft
Gabriel Luong <gabriel.luong@gmail.com> - Wed, 23 May 2018 02:00:18 -0400 - rev 798617
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1463652 - Lazy load the sourceMapURLService from the rule editor. r=pbro
MozReview-Commit-ID: Ei9g4zLO7KI
66f6b8d84e5d35d0de8d07d3e9de44a9cce913f2: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 9 - necko and docShell, r=mayhemer, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:36 +0200 - rev 798616
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 9 - necko and docShell, r=mayhemer, r=smaug
791e32d77f0f9f7772e6f798de7fc47ea055137d: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 8 - PartiallySeekableInputStream exposes nsIInputStreamLength, r=mayhemer
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:35 +0200 - rev 798615
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 8 - PartiallySeekableInputStream exposes nsIInputStreamLength, r=mayhemer
89acab76790a32927a813e826a1aad2d3e4960f1: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 7 - nsIMultiplexInputStream exposes nsIInputStreamLength, r=froydnj, r=mayhemer
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:35 +0200 - rev 798614
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 7 - nsIMultiplexInputStream exposes nsIInputStreamLength, r=froydnj, r=mayhemer
1e5e4a41b24611808b99badd32c53e044944a8a6: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 6 - nsMIMEInputStream exposes nsIInputStreamLength, r=mayhmer
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:35 +0200 - rev 798613
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 6 - nsMIMEInputStream exposes nsIInputStreamLength, r=mayhmer
14019553d3de788c3ea8250b6745b1fcd13fc283: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 5 - nsBufferedInputStream exposes nsIInputStreamLength, r=froydnj, r=mayhemer
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:35 +0200 - rev 798612
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 5 - nsBufferedInputStream exposes nsIInputStreamLength, r=froydnj, r=mayhemer
00c1f8c0e321d45680c2e7f35b962148df2096a9: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 4 - SlicedInputStream exposes nsIInputStreamLength, r=froydnj
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:35 +0200 - rev 798611
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 4 - SlicedInputStream exposes nsIInputStreamLength, r=froydnj
f6b81e43d9eca51af13ce658339792d5b8c7fc24: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 3 - InputStreamLengthHelper, r=froydnj
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:35 +0200 - rev 798610
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 3 - InputStreamLengthHelper, r=froydnj
0086783f1f566752cee7d7d4e8d9b1943682ba57: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 2 - IPCBlobInputStream exposes nsIInputStreamLength, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:35 +0200 - rev 798609
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 2 - IPCBlobInputStream exposes nsIInputStreamLength, r=smaug
2576bb7a868904099e06827f40b09308c4ee2747: Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 1 - IDL, r=mayhemer, r=froydnj, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 23 May 2018 07:12:34 +0200 - rev 798608
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1434553 - Implement nsIInputStreamLength and nsIAsyncInputStreamLength - part 1 - IDL, r=mayhemer, r=froydnj, r=smaug
133a13c44abedac2e448d315a32068ce1a5568f4: Bug 1458968. Adjust fuzz for webrender tests r=mstange
Jeff Muizelaar <jmuizelaar@mozilla.com> - Tue, 22 May 2018 21:41:33 -0400 - rev 798607
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1458968. Adjust fuzz for webrender tests r=mstange
MozReview-Commit-ID: 73Rs8QPn1xl
0f55d0ffe4949af08f11c787cc284fb51ef56387: Bug 1458968 - Create the nsDisplaySVGWrapper item in nsSVGOuterSVGAnonChildFrame, not in nsSVGOuterSVGFrame. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Tue, 22 May 2018 21:41:32 -0400 - rev 798606
Push
110803 by bmo:gl@mozilla.com at Wed, 23 May 2018 06:00:40 +0000
Bug 1458968 - Create the nsDisplaySVGWrapper item in nsSVGOuterSVGAnonChildFrame, not in nsSVGOuterSVGFrame. r=mattwoodrow
This ensures that the nsDisplaySVGWrapper's mFrame and its reference frame are the same frame: the nsSVGOuterSVGAnonChildFrame.
It'll also cause the nsDisplaySVGWrapper to be *inside* the nsDisplayTransform for the <svg> element's viewbox transform.
This patch reverts nsSVGOuterSVGFrame::BuildDisplayList to its pre-
bug 1407938 form.
(That's the bug that introduced nsDisplaySVGWrapper.)
MozReview-Commit-ID: 3jCyP6Sj8x9
