Closed Bug 895563 Opened 11 years ago Closed 11 years ago

Make Australis top area (tabs, navigation bar) use less vertical space

Categories

(Firefox :: General, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: fb+mozdev, Unassigned)

References

Details

(Whiteboard: [Australis:M-][Australis:P?])

Attachments

(2 files)

Attached image australis-top-vspace.png (deleted) —
IMHO there is a lot of vertical space in the top area of Firefox. While Australis finally brings tabs-in-titlebar (at least on Mac), there is still room for improvement. Specifically, I propose to shrink (vertically) a) the gap above tabs: The current space is about as wide as the space between a tab title and the top border, however I don't think it's necessary to use such a wide gap here. See the attachment (top area) where I reduced the gap to 4px, so 5px less, and it still does not look unbalanced! If you are worried about the user not being able to move the window around, there's enough space to the left and right (where the window and fullscreen buttons are) on which a user can click to drag the window around (the current clickable spacing of about 5px is not really helpful anyway). b) the spacing inside the #nav-bar: I reduced it to 3px (was: 4px) for both padding-top and padding-bottom in the lower half of the attachment. c) the size of a tab. This is probably the most controversal one (at least towards the UI people). I think we can gain at least 1px or 2px in the spacing both above and below the tab title. (I did not manage to produce a prototype because I could not find the "culprit" for the vertical spacing inside the tab element, neither a padding, margin, nor height property.) Adding this all up, we can easily shrink the top bar by 7px to 11px(!). In the hunt for reducing chrome area, this is a big win! I'm happy with any small gain we can agree on, but the current vertical size of the top area in Firefox is just too much.
Whiteboard: [Australis:M?]
I believe a, b and c are according to spec [1] so marking as M- as any change would be above what is specified. For a, I don't think users should have to concentrate to find a specific area on the sides of the browser in order to resize the window. We've already had bugs filed that there should be more room to drag above the tabs. australis-tabs and australis-navbar already block the australis meta bug. [1] https://people.mozilla.com/~shorlander/files/australis-designSpecs/australis-designSpecs-osx-mainWindow.html
No longer blocks: australis
Whiteboard: [Australis:M?] → [Australis:M-]
Thanks for your feedback. I expected the current design to be according to spec. However, this bug intents to change the spec in order to free up vertical space for content.
shorlander, any thoughts about this?
Sounds like this is still up in the air, but I'm moving it from UNCO to NEW since the team seems aware of the issue and is discussing it actively. Cheers!
Status: UNCONFIRMED → NEW
Component: Untriaged → General
Ever confirmed: true
Requesting needinfo? per comment 3.
Flags: needinfo?(shorlander)
Whiteboard: [Australis:M-] → [Australis:M-][Australis:P?]
The remaining space in the titlebar is for dragging the window. While reducing our chrome footprint is a goal, that has to be weighed against visual balance. Reaching the minimum possible chrome height is a non-goal. Thanks! :)
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(shorlander)
Resolution: --- → WONTFIX
Attached image australis vs chrome (deleted) —
Is taking more space than chrome's chrome does a compromise we're taking deliberately?
(In reply to Zbigniew Braniecki [:gandalf] from comment #7) > Created attachment 794757 [details] > australis vs chrome > > Is taking more space than chrome's chrome does a compromise we're taking > deliberately? Yes.
Thanks for your clarification. However, I'd still like to know what you think about (b) and (c) in comment 0. Is it possible to minimize the used space there (even if it's only a few px)? If not, can you please point me (or direct me to someone who knows) to what drives the size of the tabs? As I said I was unable to find the properties that influence their size.
The use of vertical space is especially a problem in Linux, where the window manager normally draws the title bar. Australis' tab + navigation bars take up even *more* room than they do in the current versions of Firefox, to say nothing of Chrome. It's especially stark if the user is used to the "small icons" setting (which I believe is being removed?). Florian's suggestions (b and c) look quite nice. Apologies if this is the wrong space to comment about this, as it seems OSX oriented. Thanks!
(In reply to Aibara Iduas from comment #10) > It's especially stark if the user is used to the "small icons" setting […] That mode never quite worked. I guess for those who want a smaller Australis top chrome, there'll be extensions/themes that reduce it. I may have a look into hacking together a userChrome.css that prototypes this. I have no prior knowledge of theming / writing extensions for Firefox, so I don't know if I have time to release something that is not a userChrome.css.
(In reply to Florian Bender from comment #11) > That mode never quite worked. It always worked flawlessly for me on Windows and Linux (but maybe I got lucky?). In any case I can understand why it was removed, but I don't get why the Australis theme takes up more vertical space than the old one — especially since screens have only gotten wider. Hopefully you or someone else will be able to fix that.
(In reply to Aibara Iduas from comment #12) > It always worked flawlessly for me on Windows and Linux (but maybe I got > lucky?). Word is that it didn't really change anything WRT vertical space usage. Anyway, here's what I have so far: https://www.dropbox.com/s/dfsmpaziowztf6b/australis-slimmer.png It's definitely not bug free, so it may have unwanted consequences, but it works as a proof of concept. Put that in profile-root/chrome/userChrome.css: ``` @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* set default namespace to XUL */ /* Shove AwesomeBar higher up */ #titlebar { margin-top: -8px; background: rgba(255,0,0,0.2); opacity: 0.92; } /* correct titlebar icons position */ #titlebar-content > * { margin-top: 8px; } /* Reduce the padding between the URL bar and the tabs/content */ #nav-bar-customization-target { margin-top: -2px !important; margin-bottom: -1px !important; } ```
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: