SplitView QoL Suggestion 4: Remove from SplitView and/or Swap into SplitView

[Hydraheadhunter]

I've been playing around with splitView for a few days now, and it's in an excellent state for a brand new feature, but there are some friction points that could do with some quality of life massages to really shine as a browser feature.

When you first open SplitView, you're presented with a list of tabs from that window which you can immediately add to that side of the view. I frequently have many tabs wit very similar names, and regularly click the wrong link, and the mistake is cumbersome to correct.

Say you have tabs A, B and C, and you want to have SplitView A|B but accidentally create SplitView A|C (or maybe you wanted A|C and now want to swap to A|B). The process of changing your SplitView tab configuration is 5 clicks long.

1. MB2 @ A|C
2. Seporate Split View [NEW]
3. MB2 @ A
4. Add Split View [NEW]
5. Select B from the new SplitView's menu.

This could be reduced to 3 clicks or even 2 clicks depending on implementation 

1. MB2 @ C
2. Remove from Split View (This kicks C out of the split View producing an A|0 view)
3. Select B from the new SplitView menu.

or

1. MB2 @ B
2. Replace Right-Side of Active Split View (Swaps B and C in a single Click.)

Either or both of these options would greatly reduce the friction of changing a splitView's current tabs.

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.