2061196 - Split view tabs background too narrow in collapsed vertical overflowing tab strip

Status: RESOLVED DUPLICATE of bug 2062425

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

Description

[Ben Visness [:bvisness]]

Attachment: widevert.png

The UI for split view tabs is too wide when the sidebar is compact. This applies both to the background "pill" shape (which touches the right side of the sidebar) and to the horizontal line that divides the tabs when neither is selected.

The issue is not present with standard spacing.

Comment 1

[Kelly Cochrane [:kcochrane]]

Fixed in bug 2058198

Comment 2

[Ben Visness [:bvisness]]

Attachment: narrowvert.png

Well, the background is definitely not too wide anymore, that's for sure. I'm now seeing it be too narrow.

Name: Firefox
Version: 155.0a1
Build ID: 20260810093015

Comment 3

[Kelly Cochrane [:kcochrane]]

(In reply to Ben Visness [:bvisness] from comment #2)

Created attachment 9624883 [details]
narrowvert.png

Well, the background is definitely not too wide anymore, that's for sure. I'm now seeing it be too narrow.

Name: Firefox
Version: 155.0a1
Build ID: 20260810093015

Okay can we update the bug title/description in that case please? This is only happening in compact mode when the scrollbar is present for vertical tabs.

Comment 4

[Kelly Cochrane [:kcochrane]]

Can you update the bug description as well please?

Comment 5

[Stephen Thompson [:sthompson]]

I updated the title. I see it any time the scrollbar is present for all UI densities.

I'll track this on the Nova chrome/sidebar board, but... is this a regression from container tab changes?

Comment 6

[Ben Visness [:bvisness]]

Because it turned out I was conflating several different issues, I have now put everything in bug 2062425 to try and document it all without making your lives difficult during triage.

Comment 7

[Ben Visness [:bvisness]]

I did not mean to resolve it as fixed; I think Bugzilla got confused when I refreshed the page.

Comment 8

[Stephen Thompson [:sthompson]]

Given that bug 2062425 includes this issue and we'll have someone pick up bug 2062425, I'm going to mark this as a dupe so that we don't get confused about whether this gets fixed.