Closed
Bug 1525634
Opened 6 years ago
Closed 6 years ago
"Lazy browser prematurely inserted via 'messageManager'" when moved lazy tab into new window
Categories
(Firefox :: Tabbed Browser, defect, P3)
Firefox
Tabbed Browser
Tracking
()
RESOLVED
FIXED
Firefox 67
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: Oriol, Assigned: Oriol)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
- Let a window have 4 tabs, activate the 1st one.
- Enable session restore, restart Firefox, focus that window.
- Press Shift and click the 3rd tab so that tabs 1,2,3 are multiselected with the 1st active.
- Open browser console
- Right-click a multiselected tab, chose "Move Tabs > Move to New Window"
The console shows
[bug 1345098] Lazy browser prematurely inserted via 'messageManager' property access:
getter@chrome://browser/content/tabbrowser.js:2081:37
handleEvent@chrome://browser/content/parent/ext-browser.js:458:11
addTab@chrome://browser/content/tabbrowser.js:2583:5
addWebTab@chrome://browser/content/tabbrowser.js:2267:12
adoptTab@chrome://browser/content/tabbrowser.js:3842:18
adoptRemainingTabs@chrome://browser/content/tabbrowser.js:3705:9
_beginRemoveTab@chrome://browser/content/tabbrowser.js:3031:5
swapBrowsersAndCloseOther@chrome://browser/content/tabbrowser.js:3294:10
onLoad@chrome://browser/content/browser.js:1410:9
EventHandlerNonNull*@chrome://browser/content/browser.xul:105:19
The 3rd tab in the new window is in fact lazy thanks to bug 1521346. The message above refers to the 3rd tab in the old window, which stops being lazy while being closed. It's not that bad but shouldn't happen.
Updated•6 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•6 years ago
|
||
Pushed by jwein@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5f65d978f17f
Preserve lazyness of the old tab when adopted by another window. r=jaws
Comment 3•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 67
You need to log in
before you can comment on or make changes to this bug.
Description
•