You’re conveniently ignoring the huge spacing within the floating tab. lol
That’s about 8 pixels, plus the 3 outside the tab we’re already at over 10 pixels of empty space, on both sides, making it over 20 pixels in total.
In my FF it is worse though. It’s a total of 16 pixels from the icon to the top, 19 pixels to the address bar (excluding the 1 pixel border of that). It’s like 85 pixels before I reach the website content area.
https://i.imgur.com/0MxEcW5.png
No idea why you bring other browser into this when the comparison was with older FF designs. I really don’t give a shit about any chromium browser to be honest.
I showed the other two since they’re popular, and what others would be comparing against. Firefox (on my machines) is more compact than them. So it’s not like Firefox is especially wasteful here. One has worse floating tabs, and the other has worse non-floating tabs. So it could be way worse.
Removing all the space would make it super cramped, and I don’t think it’s worth it for 10-20px. On a typical 1080p screen, that’s like 1-2% of the vertical resolution.
That said, it should be configurable. You can probably get what you want with the userChrome.css or whatever it’s called.
If they go back to non-floating tabs, you’d save like 2-3px per my screenshots. You seem to want more than that, and that’s where the accessibility issues come up.
You’re conveniently ignoring the huge spacing within the floating tab. lol That’s about 8 pixels, plus the 3 outside the tab we’re already at over 10 pixels of empty space, on both sides, making it over 20 pixels in total.
In my FF it is worse though. It’s a total of 16 pixels from the icon to the top, 19 pixels to the address bar (excluding the 1 pixel border of that). It’s like 85 pixels before I reach the website content area. https://i.imgur.com/0MxEcW5.png
No idea why you bring other browser into this when the comparison was with older FF designs. I really don’t give a shit about any chromium browser to be honest.
I showed the other two since they’re popular, and what others would be comparing against. Firefox (on my machines) is more compact than them. So it’s not like Firefox is especially wasteful here. One has worse floating tabs, and the other has worse non-floating tabs. So it could be way worse.
Removing all the space would make it super cramped, and I don’t think it’s worth it for 10-20px. On a typical 1080p screen, that’s like 1-2% of the vertical resolution.
That said, it should be configurable. You can probably get what you want with the userChrome.css or whatever it’s called.
“Others do it just as bad / even worse” is just not a good argument for making your own software worse imo.
They have other things to consider as well, such as accessibility. You can’t just eliminate all whitespace without consequences.
I do agree it should be easily configurable, but my point is that they’re better than pretty much every competitor, so I’m satisfied.
How did floating tabs improve accessibility over the previous design?
If they go back to non-floating tabs, you’d save like 2-3px per my screenshots. You seem to want more than that, and that’s where the accessibility issues come up.
I love how you didn’t answer the question and instead went on a hypothetical scenario with an outcome that is a flat out lie.