Bug 1271607 - Pinned tabs should not restore as non-remote. r=mikedeboer

App tabs load immediately, and so there's no point in causing the remoteness
flipping machinery to kick off by making the pinned tabs non-remote by default.

MozReview-Commit-ID: 48O2mJSHurr

--HG--
extra : rebase_source : 975137009468db697b20f1b05569bc7e0ec48534
This commit is contained in:
Mike Conley 2016-06-29 13:49:57 -04:00
parent 83208c5032
commit 4a3ae90945

View File

@ -2933,10 +2933,14 @@ var SessionStoreInternal = {
let userContextId = winData.tabs[t].userContextId;
let reuseExisting = t < openTabCount &&
(tabbrowser.tabs[t].getAttribute("usercontextid") == (userContextId || ""));
// If the tab is pinned, then we'll be loading it right away, and
// there's no need to cause a remoteness flip by loading it initially
// non-remote.
let forceNotRemote = !winData.tabs[t].pinned;
let tab = reuseExisting ? tabbrowser.tabs[t] :
tabbrowser.addTab("about:blank",
{skipAnimation: true,
forceNotRemote: true,
forceNotRemote,
userContextId});
// If we inserted a new tab because the userContextId didn't match with the