In order to make the history easier to navigate, this changeset includes the
modifications required to make <xul:browser> actually work as a Custom Element,
and switches the app to use it instead of the XBL browser.
Differential Revision: https://phabricator.services.mozilla.com/D14911
--HG--
extra : moz-landing-system : lando
This means that for the File URI content process, we end up closing RDM if the page
navigates. This appears to be an acceptable trade-off, as this is the behaviour we've
been shipping since bug 1453519 landed (Firefox 61).
Differential Revision: https://phabricator.services.mozilla.com/D13331
--HG--
extra : moz-landing-system : lando
Author: J. Ryan Stinnett <jryans@gmail.com>
Now that we are running about:home in the privileged content process, clicking
on a link in Activity Stream while having RDM activated will close the RDM
because a process flip will occur. This causes the following tests to time out
because the RDM has been deactivated:
- devtools/client/responsive.html/test/browser/browser_container_tab.js
- devtools/client/responsive.html/test/browser/browser_preloaded_newtab.js
This patch disables RDM in about:home and will load about:blank instead when
RDM is enabled.
MozReview-Commit-ID: D5EMyfkOM8l
--HG--
extra : source : 55c2a8d227dc91f965718aa09da9811cff0969a7
extra : intermediate-source : 4fe4ec18f2f3a4ed521205402de44b0987bae657
extra : histedit_source : a8107ebd47e63502f29c8b49b4967e15e0f0624a
Author: J. Ryan Stinnett <jryans@gmail.com>
Now that we are running about:home in the privileged content process, clicking
on a link in Activity Stream while having RDM activated will close the RDM
because a process flip will occur. This causes the following tests to time out
because the RDM has been deactivated:
- devtools/client/responsive.html/test/browser/browser_container_tab.js
- devtools/client/responsive.html/test/browser/browser_preloaded_newtab.js
This patch disables RDM in about:home and will load about:blank instead when
RDM is enabled.
MozReview-Commit-ID: D5EMyfkOM8l
--HG--
extra : rebase_source : a9a2aab3076a84b202176ca75bc9390315a5d5bf
extra : intermediate-source : f8a06d01437e3626189c60f1a87ff7038fb328ed
extra : source : 55c2a8d227dc91f965718aa09da9811cff0969a7
Author: J. Ryan Stinnett <jryans@gmail.com>
Now that we are running about:home in the privileged content process, clicking
on a link in Activity Stream while having RDM activated will close the RDM
because a process flip will occur. This causes the following tests to time out
because the RDM has been deactivated:
- devtools/client/responsive.html/test/browser/browser_container_tab.js
- devtools/client/responsive.html/test/browser/browser_preloaded_newtab.js
This patch disables RDM in about:home and will load about:blank instead when
RDM is enabled.
MozReview-Commit-ID: D5EMyfkOM8l
--HG--
extra : rebase_source : 40ab33f73463dfacd680823ba81e856d58ebc967
extra : source : 55c2a8d227dc91f965718aa09da9811cff0969a7
For simplicity, we do not support remote-to-non-remote or non-remote-to-remote
nsIWebProgressListener persistence.
Differential Revision: https://phabricator.services.mozilla.com/D7936
--HG--
extra : moz-landing-system : lando
Remove the _manifestURI field and handling of the MozApplicationManifest message.
Differential Revision: https://phabricator.services.mozilla.com/D5336
--HG--
extra : moz-landing-system : lando
Prior to bug 1453751 responsive design mode relied on the parent process seeing
that no favicon had been loaded and so defaulting to the root favicon for a
site. This would have meant that on some occasions responsive design mode didn't
show the correct favicon for pages that specified their own. This change passes
all the link related messages to the parent so favicons, feeds and searches
should work correctly.
Differential Revision: https://phabricator.services.mozilla.com/D3032
--HG--
extra : moz-landing-system : lando
I generally tried to preserve the behavior of consumers where they treated an
exception from getInterface(Ci.nsIContentFrameMessageManager) as a signal to use
some sort of fallback.
I did change the behavior of consumers that walked up to the root same-type
docshell before getting the message manager to just get it directly from the
docshell they have. Please review those parts carefully, and let me know if you
want me to ask some subject area experts to review those.
I generally tried to preserve the behavior of consumers where they treated an
exception from getInterface(Ci.nsIContentFrameMessageManager) as a signal to use
some sort of fallback.
I did change the behavior of consumers that walked up to the root same-type
docshell before getting the message manager to just get it directly from the
docshell they have. Please review those parts carefully, and let me know if you
want me to ask some subject area experts to review those.
This fixes the case of navigating a container tab from about:newtab to a remote
site. This case triggers the process flip machinery where parent process is
told to manage the load. We needed to allow certain session store messages for
this to complete successfully.
--HG--
extra : rebase_source : bb89e430941039d13a5352c9fc21777844de94e4
This adds support for container tabs / contextual identity in Responsive Design
Mode. Tabs in non-default contexts can now be opened in RDM just like regular
tabs.
MozReview-Commit-ID: BofTgrowjGV
--HG--
extra : rebase_source : 171f6d0579ef3528160729b964d1cc71e1d74386
Also fixes existing code which fails the rule.
MozReview-Commit-ID: CkLFgsspGMU
--HG--
extra : rebase_source : 86a43837659aa2ad83a87eab53b7aa8d39ccf55b
Use `E10SUtils` to check for cases where browser code would try to force a
browser to reselect a new process (such as when it is a preloaded browser) so
that we can avoid any process changes once RDM is open.
If such a case applies, navigate to about:blank first to trigger the process
change before starting RDM.
MozReview-Commit-ID: CxspLFXXotF
--HG--
extra : rebase_source : cb94789344f17c0b51ff4afbb54921218a2dd1b5
Manually-implemented QueryInterface functions don't benefit from the
MozQueryInterface optimizaions, and a lot of them are in hot code, and
implement a large number of interfaces.
MozReview-Commit-ID: 8OzglraowZt
--HG--
extra : rebase_source : 5fff3d9973a0ea976096339a63ce9ff628b68441
This also removes any redundant Ci.nsISupports elements in the interface
lists.
This was done using the following script:
acecb401b7/processors/chromeutils-generateQI.jsm
MozReview-Commit-ID: AIx10P8GpZY
--HG--
extra : rebase_source : a29c07530586dc18ba040f19215475ac20fcfb3b
RDM frames with their custom message manager hadn't exposed a value for
`processMessageManager`. This was just a oversight.
By adding this value, we get a working Browser Content Toolbox for RDM tabs.
MozReview-Commit-ID: 95QskEMKgZK
--HG--
extra : rebase_source : 5259800f64afe55ee5bca29492f6f33efcfd458c
