Closed Bug 1244317 Opened 9 years ago Closed 8 years ago

[e10s] Possible to end up with 0 (zero) visuallyselected="true" tabs

Categories

(Firefox :: Tabbed Browser, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1157404
Tracking Status
e10s + ---
firefox47 --- affected

People

(Reporter: arni2033, Unassigned)

References

Details

Based on bug 1157404 comment 12 STR (approximate): 1. Open 5 tabs with http://www.rp-online.de/ in a new window (there should be only 5 tabs and each of them should be http://www.rp-online.de/) 2. Do {press Ctrl+Tab, then Ctrl+R} (x5 times) 3. Close current tab (Ctrl+W) 4. When it's closed, reopen that tab (Ctrl+Shift+T) 5. Immediately closed it (Ctrl+W) 6. While the tab from Step 5 is still not closed, switch to the next tab (Ctrl+Tab) [Sometimes while that tab still is not visually selected, the tab from Step 5 closes, and the current tab will never become visually selected (unless I switch between tabs)] AR: There's no visually selected tab ER: Current tab should be visually selected Note: 1) It's known fact that when I switch to tab, it doesn't immediately becomes visually selected (see bug 1183135). But apparently, if that doesn't happen before the currently visually selected tab closes, the new selected tab doesn't become visually selected at all. 2) Interestingly, current tab after Step 6 has [selected], [first-visible-tab] and [afterselected] attributes, but not [visuallyselected]. 3) I haven't found reliable STR yet, because timeout of "becoming visually selected" is unpredictable. If it's really too hard to reproduce, you can ask me to investigate some simple things using Browser toolbox (though I don't have time to "build") > screenshot: https://dl.dropboxusercontent.com/s/mr50ob5bjry2tqu/bug%201157404%20comment%2010.png > screencast: https://dl.dropboxusercontent.com/s/yfoj1tvj38soib5/screencast%201%20-%20zero%20visuallyselected.webm?dl=0 On the screencast, I try to reproduce this 3 times, and the 3rd attempt is successful.
tracking-e10s: --- → +
Priority: -- → P3
I tested it a month ago on Nightly 2016-10-01 and found fix range - it was fixed by bug 1157404
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.