1253543 - firefox OS X fullscreen not limited by pinned-tab width

Status: NEW

(Firefox :: Toolbars and Customization, defect, P3)

Description

[JMoVS]

Attachment: a.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160210153822

Steps to reproduce:

Have some pinned tabs. Go into Mac OS El Capitan's side-by-side fullscreen. Resize the firefox side of the split screen.
I have 8 pinned-tabs in this case.


Actual results:

The split screen part of Firefox can be made smaller than the minimum width required to show all pinned tabs + one of the regular tabs. This means I see only the first 3 pinned-tabs and cannot scroll through them or switch to my actual none-pinned tabs.


Expected results:

I see 2 ways forward:
1: Specifiy minimum size according to the space required for pinned-tabs + 1 tab to display properly so I can reach usual tabs as well as all pinned-tabs
2: Make pinned-tabs scrollable as well as usual tabs in this case

I would personally prefer (1) as it seems cleaner to me. See the attached screenshot for a demonstration of the problem of (a) before resize and (b) after resize.

Comment 1

[JMoVS]

Attachment: b.png

Comment 2

[Tracy Walker [:tracy]]

I had to have over 20 tabs pinned on my MacBookPro to reproduce this. (don't know how to resize the Firefox side of the split full screen), Bu tit is reporducible with latest Nightly 49.0a1, 20160531030258.

Comment 3

[JMoVS]

if you have a firefox window and another window (eg Mail.app) open, long pressing and holding on the green button will give you the option to have split view. You can then just grab the middle between the two fullscreen windows and resize it accordingly to be able to more easily reproduce this bug.

Comment 4

[Stephen A Pohl [:spohl] (OOO until 3/13)]

Markus, do you know if this requires any widget:cocoa changes? It seems like this is frontend related and would fit better in Firefox > General.

Comment 5

[Markus Stange [:mstange]]

You're right, this only needs frontend changes.

I've confirmed that setting "min-width:auto" on #TabsToolbar, #navigator-toolbox and #main-window fixes this, but those things have a non-auto min-width for a reason so that change would probably cause regressions.