2012231 - Unexpected shift to Left Splitview when Right Splitview tab is active

Status: RESOLVED WORKSFORME

(Firefox :: Tabbed Browser: Split View, defect, P2)

Description

[Natalie Stroud [:nstroud]]

Ways to turn on Split View:

1 tab method
Open Firefox Nightly
Open any website
Open a tab context menu on any tab in the tab strip
Select ‘Add Split View’

2 tab method
Open Firefox Nightly
Open two websites in two separate tabs
In the tab strip, select one tab and press Ctrl + SPACE + left/right arrow key to select the second tab
Open the tab context menu
-for keyboard on Windows, you'll want to press fn + Shift + F10 to get to the context menu
Select ‘Add Split View’

STR:

1. Turn on splitview using the 1 tab method mentioned above. Make sure that the Right Splitview screen is the 'Choose a tab to add to split view' page
2. Using the TAB key, begin to move keyboard focus into the splitview
3. Observe the behavior/focus switch once you have entered the splitview screens

Actual:

When the Right Splitview contains the 'Choose a tab to add to split view' page and a user moves keyboard focus off of the tab strip and to the splitview, focus drops into the non-active Left Splitview screen. This also makes the Right Splitview non-active, and the Left Splitview goes from non-active to active

[note: this only seems to occur when the Right Splitview is the 'Choose a tab to add to split view' page. When Right Splitview contains a website the issue does not occur]

Expected:

The Right Splitview should remain active if a user is moving keyboard focus from the tab strip to the splitview. This is especially important since this occurs with the 'Choose a tab to add to split view' and a keyboard user is trying to reach the screen to make a selection

Comment 1

[Sam Foster [:sfoster] (he/him)]

I'm not able to reproduce from these STR, but the symptoms sounds a lot like Bug 2014310. If that lands and seems to fix the issue here, we can close as a duplicate.

Comment 2

[Nikki Sharpley (:nikkis) (she/her)]

This appears to be fixed. Please reopen if this occurs again.