Closed
Bug 1275277
Opened 7 years ago
Closed 5 years ago
[e10s] When a window has only 1 tab that has about:blank loaded in the parent process, moving the tab out of the window does not close the window
Categories
(Firefox :: Tabbed Browser, defect, P5)
Tracking
()
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: dw-dev, Unassigned)
References
Details
(Whiteboard: [tabs] triaged)
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 20160502172042 Steps to reproduce: In my Tile Tabs add-on, I use chrome.tabs.move to move tabs from one window to another. Sometimes, moving the last tab out of a window does not cause the window to close. Specifically, if the last tab in a window (A) is a non-e10s "about:blank" tab, then moving it to another window (B) does not cause window (A) to close. Instead the "about:blank" remains in window (A) and another "about:blank" tab appears in window (B). However, if the last tab in a window (A) is a non-e10s "about:newtab" tab, then moving it to another window (B) does cause window (A) to close. Actual results: The non-e10s "about:blank" tab remains in window (A) and is duplicated in window (B), and window (A) does not close. Expected results: The non-e10s "about:blank" tab should be moved from window (A) to window (B), and window (A) should be closed.
Updated•7 years ago
|
Component: WebExtensions → Tabbed Browser
Product: Toolkit → Firefox
Summary: WebExtensions: Moving the last tab out of a window does not always close thw window → Moving the last tab out of a window does not always close the window
Comment 1•7 years ago
|
||
Probably not super-high priority because it's pretty hard to end up with a tab like that...
Status: UNCONFIRMED → NEW
tracking-e10s:
--- → ?
Ever confirmed: true
Summary: Moving the last tab out of a window does not always close the window → [e10s] When a window has only 1 tab that has about:blank loaded in the parent process, moving the tab out of the window does not close the window
Comment 2•7 years ago
|
||
Does it only happen in a non-e10s window? If so, this may be wontfix as non-e10s windows will eventually be going away.
Blocks: e10s-addons
Comment 3•7 years ago
|
||
(In reply to Tracy Walker [:tracy] from comment #2) > Does it only happen in a non-e10s window? If so, this may be wontfix as > non-e10s windows will eventually be going away. No. Tabs can still be "non e10s" in e10s windows, in that they load pages that are loaded in the parent process (like about:preferences). If we then load another page that does not require a switch to another process (like about:blank) then certain functionality behaves differently. That bug will continue to exist when we get rid of non-e10s windows.
Updated•7 years ago
|
Priority: -- → P5
Whiteboard: [tabs] triaged
Comment 4•5 years ago
|
||
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•