9883f547e28008de9ee595492c8732d9cdc4e294: Bug 1488849 - Don't fail when a chunk is not running any test when the try selector is 'coverage'. r=ahal
Marco Castelluccio <mcastelluccio@mozilla.com> - Fri, 23 Nov 2018 17:59:04 +0100 - rev 449382
Bug 1488849 - Don't fail when a chunk is not running any test when the try selector is 'coverage'. r=ahal
8c51ad4a6b724e6146488e1b93ae92ba4d7fdce8: Bug 1450784 - Add a new error page for MOZILLA_PKIX_ERROR_MITM_DETECTED. r=nhnt11,keeler
Johann Hofmann <jhofmann@mozilla.com> - Mon, 26 Nov 2018 10:17:58 +0100 - rev 449381
Bug 1450784 - Add a new error page for MOZILLA_PKIX_ERROR_MITM_DETECTED. r=nhnt11,keeler Differential Revision: https://phabricator.services.mozilla.com/D12874
c84eefa8a511b9c3684e98eb3a0a0cbb7d290f06: Bug 1505257 - add nglayout.debug.paint_flashing_chrome to paint debug pref value list r=mstange
A. Wilcox <AWilcox@Wilcox-Tech.com> - Wed, 07 Nov 2018 04:50:21 +0000 - rev 449380
Bug 1505257 - add nglayout.debug.paint_flashing_chrome to paint debug pref value list r=mstange
62f498382b14816950a6568513354ecbabe05245: Backed out 11 changesets (bug 1500948, bug 1500949, bug 1510460, bug 1509362, bug 1487249, bug 1511237, bug 1500950, bug 1500944) for causing bug 1485566 to permafail on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Tue, 04 Dec 2018 22:39:01 +0200 - rev 449379
Backed out 11 changesets (bug 1500948, bug 1500949, bug 1510460, bug 1509362, bug 1487249, bug 1511237, bug 1500950, bug 1500944) for causing bug 1485566 to permafail on a CLOSED TREE Backed out changeset 788d4d999843 (bug 1511237) Backed out changeset 78d93dade802 (bug 1510460) Backed out changeset 7e23a1b90335 (bug 1509362) Backed out changeset 9fe159adaef4 (bug 1500950) Backed out changeset 622d4bf1c0ef (bug 1500949) Backed out changeset 8f8c74fb660d (bug 1500948) Backed out changeset b4617d90fd55 (bug 1500944) Backed out changeset 3978df88b38b (bug 1500944) Backed out changeset 7a1bb48d843f (bug 1487249) Backed out changeset ba592aebdba2 (bug 1487249) Backed out changeset a6604d042a96 (bug 1487249)
3285b6018d3aa3d02e8a1f4b359e3aaeab58d8d2: Backed out changeset 05e25df4db43 (bug 1450784) for failing bc at browser/base/content/test/static/browser_misused_characters_in_strings.js on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Tue, 04 Dec 2018 22:28:23 +0200 - rev 449378
Backed out changeset 05e25df4db43 (bug 1450784) for failing bc at browser/base/content/test/static/browser_misused_characters_in_strings.js on a CLOSED TREE
5d2f9b45ad97f636627f1618519c26362aa080df: Bug 1337655 followup: Only turn off moz-prefixed gradients on Nightly for now, since some sites still use them. rs=emilio
Daniel Holbert <dholbert@cs.stanford.edu> - Tue, 04 Dec 2018 14:45:24 -0500 - rev 449377
Bug 1337655 followup: Only turn off moz-prefixed gradients on Nightly for now, since some sites still use them. rs=emilio In particular, Zimbra apparently still relies on moz-prefixed gradients for Firefox users, so let's avoid breaking Zimbra for beta users. I'm working on getting Zimbra fixed so that this can eventually ride the trains, though, barring other bustage that can't be addressed via outreach...
05e25df4db432b6f877658287774d52adf758c43: Bug 1450784 - Add a new error page for MOZILLA_PKIX_ERROR_MITM_DETECTED. r=nhnt11,keeler
Johann Hofmann <jhofmann@mozilla.com> - Mon, 26 Nov 2018 10:17:58 +0100 - rev 449376
Bug 1450784 - Add a new error page for MOZILLA_PKIX_ERROR_MITM_DETECTED. r=nhnt11,keeler Differential Revision: https://phabricator.services.mozilla.com/D12874
20c76341695be6f3a382460814492c95393da5d7: Bug 1511883 - The secondary pane should persist its size. r=dwalsh
Jason Laster <jlaster@mozilla.com> - Mon, 03 Dec 2018 16:37:33 -0500 - rev 449375
Bug 1511883 - The secondary pane should persist its size. r=dwalsh Tags: Bug #: 1511883 Differential Revision: https://phabricator.services.mozilla.com/D13695
72633f72bd41bff1edd3cdc3d870b10c869b3b22: No bug: Fix some rst errors in taskcluster documentation; r=me
Tom Prince <mozilla@hocat.ca> - Tue, 04 Dec 2018 11:35:32 -0500 - rev 449374
No bug: Fix some rst errors in taskcluster documentation; r=me
788d4d99984316782178133ba3bdab6b5742644a: Bug 1511237 - Store a TabChild reference in cached docshells, r=bzbarsky, r=smaug
Nika Layzell <nika@thelayzells.com> - Thu, 29 Nov 2018 20:27:08 -0500 - rev 449373
Bug 1511237 - Store a TabChild reference in cached docshells, r=bzbarsky, r=smaug Differential Revision: https://phabricator.services.mozilla.com/D13489
78d93dade802d5a285fe718284310a397be97acb: Bug 1510460 - Record the current WindowGlobal on ChromeBrowsingContext, r=farre
Nika Layzell <nika@thelayzells.com> - Tue, 27 Nov 2018 15:03:05 -0500 - rev 449372
Bug 1510460 - Record the current WindowGlobal on ChromeBrowsingContext, r=farre Differential Revision: https://phabricator.services.mozilla.com/D13156
7e23a1b903356b3bdfbf1844bee62513969b93a6: Bug 1509362 - Don't crash when constructing actor during content shutdown, r=jld
Nika Layzell <nika@thelayzells.com> - Thu, 22 Nov 2018 13:40:32 -0500 - rev 449371
Bug 1509362 - Don't crash when constructing actor during content shutdown, r=jld When shutting down a content process, we call `Close` on the `IToplevelProtocol`. This causes the MessageChannel to be `Close`-ed, which in turn sends a `GOODBYE_MESSAGE`: https://searchfox.org/mozilla-central/rev/876022232b15425bb9efde189caf747823b39567/ipc/glue/MessageChannel.cpp#2852 This message is intercepted on the I/O thread in the content process, before any code is informed in content, and used to set the `mChannelState` property to `ChannelClosing`: https://searchfox.org/mozilla-central/rev/876022232b15425bb9efde189caf747823b39567/ipc/glue/MessageChannel.cpp#1176 Once this state has been set, which is performed as soon as the message is received, whether or not other messages have been processed yet, no messages can be sent back to the parent process. This is usually what causes the 'Too late to send/recv' message spam in the console, as we're still trying to send messages at this time. Usually this is fine - the message send fails, but we gracefully recover, and the process begins shutting down like normal. Unfortunately, child actor constructors currently have code automatically generated in them which causes a process crash if the send fails. As it's impossible for the main thread to know that the channel has been closed ahead of time (due to this happening out-of-band), we can then cause random content process crashes during shutdown due to actor construction. Unfortunately, we can't just destroy the actor, as our caller may (and often do) depend on the actor reference they gave us still being valid after calling Send*Constructor. Fortunately, if a message send failed, it means we're in the process of being shut down. This patch handles this by ignoring ctor send errors, and treating them like messages which successfully were queued to send, but got lost due to the other side hanging up. The actor will be gracefully destroyed in DestroySubtree when its manager is destroyed. Differential Revision: https://phabricator.services.mozilla.com/D12695
9fe159adaef4b0ab58cf16969f70a75e4ef2e546: Bug 1500950 - Expose rootFrameLoader on WindowGlobalParent, r=farre
Nika Layzell <nika@thelayzells.com> - Sat, 20 Oct 2018 19:39:02 -0400 - rev 449370
Bug 1500950 - Expose rootFrameLoader on WindowGlobalParent, r=farre This attribute was not exposed due to Bug 1489301. Differential Revision: https://phabricator.services.mozilla.com/D9404
622d4bf1c0efe87d3128bc89903cb515487d69f4: Bug 1500949 - Include innerWindowId/outerWindowId in PWindowGlobal, r=farre
Nika Layzell <nika@thelayzells.com> - Sat, 20 Oct 2018 16:04:00 -0400 - rev 449369
Bug 1500949 - Include innerWindowId/outerWindowId in PWindowGlobal, r=farre This will be useful as both an ID for PWindowGlobal, as well as a mechanism for taking advantage of already synchronized information. As an example, LoadInfo objects contain the inner window IDs of the window requesting the load, which can now be used to obtain a reference to the corresponding WindowGlobalParent in the parent process. Differential Revision: https://phabricator.services.mozilla.com/D9396
8f8c74fb660dd36cf873f9aa82c3487aea951876: Bug 1500948 - Expose BrowsingContext on nsFrameLoader objects, r=farre
Nika Layzell <nika@thelayzells.com> - Fri, 19 Oct 2018 20:02:37 -0400 - rev 449368
Bug 1500948 - Expose BrowsingContext on nsFrameLoader objects, r=farre This should make BrowsingContext more usable by making it much easier to obtain for a given frame or browser. BrowsingContext and nsFrameLoader should have the same lifetime. Differential Revision: https://phabricator.services.mozilla.com/D9395
b4617d90fd5527c145b5a11d11553b22eaae15f6: Bug 1500944 - Part 2: Expose WindowGlobal actors to Chrome JS, r=farre
Nika Layzell <nika@thelayzells.com> - Fri, 19 Oct 2018 19:02:56 -0400 - rev 449367
Bug 1500944 - Part 2: Expose WindowGlobal actors to Chrome JS, r=farre This serves 2 purposes: 1. Provides an object corresponding to an inner window which Chrome JS can hold onto. 2. Provides the object to JS which Chrome JS per-window actors will be attached to. 3. Provides useful information to Chrome JS in the parent process. Differential Revision: https://phabricator.services.mozilla.com/D9394
3978df88b38b739e0e2754436b9e29bac82e5cc1: Bug 1500944 - Part 1: Store the set of active WindowGlobalParent objects in ChromeBrowsingContext, r=farre
Nika Layzell <nika@thelayzells.com> - Fri, 19 Oct 2018 18:00:59 -0400 - rev 449366
Bug 1500944 - Part 1: Store the set of active WindowGlobalParent objects in ChromeBrowsingContext, r=farre This allows getting the set of all window globals for a given browsing context. This is less useful at the moment as the active window global is not exposed as such. That will be added as a follow-up. Differential Revision: https://phabricator.services.mozilla.com/D9393
7a1bb48d843f4396e6d95f3cdda5dd7c70292974: Bug 1487249 - Part 3: Add the WindowGlobal actor representing a single window global, r=bzbarsky
Nika Layzell <nika@thelayzells.com> - Wed, 29 Aug 2018 18:21:25 -0400 - rev 449365
Bug 1487249 - Part 3: Add the WindowGlobal actor representing a single window global, r=bzbarsky This actor can be used for communicating with individual frames, without depending on walking the tree in the content process. This is not yet complete. No tests have been written for it, the WindowGlobalParent objects need to be exposed to chrome JS, and a form of JS actors should be installed under them. In addition, BrowsingContextChrome objects should be updated to allow access to the current WindowGlobalParent in that context. Differential Revision: https://phabricator.services.mozilla.com/D4623
ba592aebdba2586dd7dd36b7940912fc5cdf5357: Bug 1487249 - Part 2: Add a new PInProcess actor to manage intra-thread actors, r=mccr8
Nika Layzell <nika@thelayzells.com> - Wed, 29 Aug 2018 18:18:04 -0400 - rev 449364
Bug 1487249 - Part 2: Add a new PInProcess actor to manage intra-thread actors, r=mccr8 This will be useful as a basis for asynchronous actors which would like to exist both when crossing the process boundary (managed by PContent), and when displaying an in-process window. Differential Revision: https://phabricator.services.mozilla.com/D4622
a6604d042a9661b0eedd27f3a2095a56a5097ba5: Bug 1487249 - Part 1: Allow MessageChannel objects to be created within a thread, r=mccr8
Nika Layzell <nika@thelayzells.com> - Wed, 29 Aug 2018 18:00:05 -0400 - rev 449363
Bug 1487249 - Part 1: Allow MessageChannel objects to be created within a thread, r=mccr8 To create a more generic interface for interacting both within the main thread of the parent process and between the parent and child processes, it would be nice to support IPDL actors within the main thread of the parent process. This requires the underlying MessageChannel actor to support intra-thread links. This change adds support for intra-thread links to the underlying MessageChannel object using ThreadLink, and an extra boolean flag. Differential Revision: https://phabricator.services.mozilla.com/D4620
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip