Dão, the only problem (as far as I can tell) with this patch is that there is no tab separator before the first non-pinned tab when the tabstrip is overflowing. A CSS-only solution might be to use a selector like .tabbrowser-tab[pinned] + .tabbrowser-tab:not([pinned]), but I worry about hidden tabs in between. Do you think this would be an OK solution or should we try and add an attribute to the first visible non-pinned tab in JavaScript for styling convenience?
Dão, the only problem (as far as I can tell) with this patch is that there is no tab separator before the first non-pinned tab when the tabstrip is overflowing. A CSS-only solution might be to use a selector like .tabbrowser- tab[pinned] + .tabbrowser- tab:not( [pinned] ), but I worry about hidden tabs in between. Do you think this would be an OK solution or should we try and add an attribute to the first visible non-pinned tab in JavaScript for styling convenience?