Bug 1253382 - Force the initial browser remoteness only after the browser's onLoad has fired. r=jmaher

This is necessary in order to be able to open new tabs from the initial
browser window, since the initial browser window needs to have its
BrowserDOMWindow attribute set when it goes remote - and if it fires
before the onLoad handler in browser.js, the BrowserDOMWindow attribute
that's set on the XUL window (which gets copied over to the remote browser),
hasn't been set yet.

MozReview-Commit-ID: AYyFdyoX8g9

--HG--
extra : rebase_source : ca2728e3c059e26eba09e57ee883c8ca1623631e
This commit is contained in:
Mike Conley 2016-03-03 18:15:12 -05:00
Родитель bc43c5edfc
Коммит 0ab3965084
3 изменённых файлов: 21 добавлений и 21 удалений

Просмотреть файл

@ -225,6 +225,10 @@ function plInit() {
return E10SUtils.canLoadURIInProcess(pageUrls[0], Ci.nsIXULRuntime.PROCESS_TYPE_CONTENT);
}
// do this half a second after load, because we need to be
// able to resize the window and not have it get clobbered
// by the persisted values
setTimeout(function () {
// For e10s windows, the initial browser is not remote until it attempts to
// browse to a URI that should be remote (landed at bug 1047603).
// However, when it loads such URI and reinitialize as remote, we lose the
@ -245,10 +249,6 @@ function plInit() {
// Implicit else: initial browser in e10s is non-remote by default.
}
// do this half a second after load, because we need to be
// able to resize the window and not have it get clobbered
// by the persisted values
setTimeout(function () {
browserWindow.resizeTo(winWidth, winHeight);
browserWindow.moveTo(0, 0);
browserWindow.focus();

Просмотреть файл

@ -4,7 +4,7 @@
xmlns:em="http://www.mozilla.org/2004/em-rdf#">
<Description about="urn:mozilla:install-manifest">
<em:id>pageloader@mozilla.org</em:id>
<em:version>1.0.2</em:version>
<em:version>1.0.4</em:version>
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>

Двоичный файл не отображается.