Firefox 89 Tab Appearance
amitp.blogspot.com
amitp.blogspot.com
Browser Tool Box (open fly out menu -> More Tools, or Ctrl+Alt+Shift+I). This opens a remote debugging session, and you can freely select and customize any part of the chrome.
I’m still confused why the tabs look like this. The active tab is so different than the inactive that it’s hard to make a connection between them. Most people already have an association with typical tab UIs. Why change this fundamental perception into something more generic and ambiguous?
It doesn't justify shitty UX decisions, no. But it does alleviate the pain you experience when companies (inevitably) do fuck up something you depend on.
If the same happened in Chrome or Safari you would have the same chance of adjusting the browser UI as you have adjusting the UX of your toaster (none [or with a lot of work]).
Instead, Firefox lets power users be power users, installing extensions that completely changes the UI or adding your own stylesheets for customizations like the ones mentioned in this submission.
So booo to the team doing the UX change, yay to Firefox for letting me fix their own mistakes without having to wait for it to be deployed.
> Most people already have an association with typical tab UIs. Why change this fundamental perception into something more generic and ambiguous?
This was probably said about tabs vs windows when tabs first appeared in browsers as well. Why introduce a different concept when you can already have many windows?! People seem to prefer tabs today, so sometimes going against the wind is a good thing. Problem is that you don't know what will be good until you throw that thing at people and they tell/show you their reaction.
You can justify any bad changes this way and "probably" means you don't know but you just made it up to justify. Tabs made things better we all new when that happend. What good thing the designers thought to introduce this change like in the tabs?
These designers have nothing to do at office if they don't. Basically we all are lab rats with every new shiny device or app version that hits now a days. Anyone having fun re-learning new gestures on mobile devices every 2 years?
My biggest gripe is that the default UI doesn’t look like a typical default UI. It looks like a third party plugin that’ll most likely confuse more people than with a plain boring UI.
Tabs is a way to group related so windows which useful if you have many of them. And AFIR tabs in browsers was very welcomed by users, unlike today’s nonstop UI churn.
Why listen to feedback when you have telemetry. (edit: /s for clarity. My point is that telemetry is probably a net negative for many projects.)
There's probably a telemetry -> spreadsheet -> powerpoint -> jira workflow that people are doing full time at most companies.
Telemetry complements feedback, it should never replace it entirely.
The problem is that every major UI change breaks the userChrome.css and I have to spend a while tweaking it or waiting for someone else to design it up. It's frustrating.
Since I knew this update was coming I disabled automatic updates for the first time ever. It might be a while before I decide to upgrade.
ESR is definitely a safer option.
If you use a lot of tabs in most browsers, the tabs end up being just tiny icon-sized. That's no good. I also don't want to go through another layer to find them.
After using it, I simply don't care. It's fine either way to me.
So I switched to Firefox a few months back... It's disappointing that they've now made exactly the same mistake, but at least there's Firefox Color [1] that allows me to easily restore some contrast without spending time writing my own CSS.
But I don't know why I hardly noticed a difference. I mean sure it does look like a button, and I don't really get the point of it, but the thing I was worried about was the increased screen estate. Maybe it's because of my gtk theme, maybe it's related to fixes in hidpi UI scaling, but it actually seems to use less screen estate to me.
Am I crazy? Or are there other people that feel like its using less screen estate?
I applied a browser CSS change to fix it, and now I think it's great.
/*
* remove dead space in browser tabs bar
*
* Source: https://www.reddit.com/r/firefox/comments/nq6kto/if_you_dont_like_the_new_design_you_can_disable_it/
*/
:root { --tab-min-height: 30px !important; }
:root #tabbrowser-tabs { --tab-min-height: 30px !important; }about:config
I have the new tab theme, and the compact UI once again.
And if anyone is also trying this route - change `browser.uidensity` to 1 will restore the compact theme.
Anyway looked a lot worse in screenshots, with my system theme and tweaks I am actually liking how it looks. What I don't like very much is the new shield icon inside the address bar, looks more like a weird hexagon than a shield, but that's rather minor.
Personally it's unusable on my Windows 7 computer. I know it's a dead OS but still.
On a different note, is there a way to have "send tab to another device" as a dedicated button again? They moved it as a sub-item unter the "firefox account" button, this is much less conventient as it was. The send tab feature is one of my most used features.
I just hope this endless tinkering with things that aren't broken ends someday -- users don't need an A/B-calculated productivity increase of 2%, come back when you can increase it by 200%. But in that case, just make another product and leave existing working ones alone.
https://github.com/black7375/Firefox-UI-Fix/
It's well commented enough that you should be able to cherry-pick individual fixes.
I think this is a more general problem with dark-mode interfaces. Contrast of content is usually easy to achieve (e.g. light text on dark background) but getting contrast between UI elements like tabs is quite difficult.
Apple had a great talk about the design challenges at WWDC 2019. One of the ways they do this is by integrating ambient colours from things like the desktop wallpaper which Firefox doesn't do.
In one word: Why?
In two words: Why not?
(Joking, it is a textbook example of ergonomic regression for the sake of change).
The customizability in Firefox is great, but the example in the link is... well, to each their own.
Agreed, and the linked article specifically themes their tabs to look like a file folder, with a reminiscent color and rounded corners.
The very concept of a tab that contains related information in it is a replication of the physical tabbed file folder.
It's pretty much this: https://imgur.com/a/u2WgESW
And that is largely a hold over from the concept of a physical desktop in an office. See: https://onezero.medium.com/the-document-metaphor-desktop-gui...
It'd be nice for some new concepts to be introduced and refined.
Only Safari kept this UX. I never understood why everybody copied this Chrome thing.
You’ve changed my mind on this.
If "the element is connected to the content it represents" is enough to make a design skeuomorphic then so be it but either way I don't think it's desired "because that's how real folders work" vs "I want to know which UI elements are related".
It looks and feels FAST!
A skeuomorph is just an unessential design cue a derivative takes from the original. They can be entirely ornamental (like the dumb faux leather of some of the latter day Jobs-era iOS apps), but they're quite useful as affordances.
There's no particular technical reason why you'd prefer any one particular graphic design for tabs over another, but the separator-style tabs make the association between tab headers and contents much clearer than the new design.
Likewise, there's a lot of value in the Numi/Soulver style of calculator apps for power users, but common users are better served by the skeuomorphic physical calculator design, which is perfectly functional and much more familiar to most (though this may change as younger generations are less and less exposed to traditional calculators).
They also removed the icons in the menu that helped me navigate. Now I have to read the menu more carefully to see what I'm doing. Definitely slower than a few days ago.
Final insult, they hard coded the highlight colors in about:* to cyan! I hate cyan. Dark mode panels have a blue tinge to them. Is this amateur hour or what? I use warm colors with my dark mode, on purpose. Not anymore.
I had to disable the also ridiculous animated expanding url bar in the previous release with userChrome. I'm done with that. Designers, please go experiment on some other app, not the one I rely on every day.
My educated guess is that someone working in a private company has to justify their salary, even when there is nothing to do. So they come up with "absolutely necessary work to do" by inventing themselves solutions and "improvements" for problems nobody has.
Now we have a team of +10 people doing meetings, colorful charts, analysis, etc. Including writing blog posts like "changing the world and fighting a pandemic by changing the size of the tabs". Bosses raise the head and see all the cubicles busy. Everybody is happy.
Now that it's released it's time to think about the changes for the next version.
PS: I'm a happy Firefox user since it was just "mozilla".
2) for years now, tech companies have hired enough designers for the boom periods, rather than contracting or just dealing with longer design cycles—I suspect this is Apple's influence leading to much larger design budgets and resultant empire-building.
3) bust-period design work doesn't get one promotions or look as impressive in a portfolio as boom-period design work, so design departments or individuals are heavily incentivized to create artificial "booms" both so they have enough work to do and so that the work is helping everyone advance their career. These align well with product manager career advancement incentives (everyone loves screen shots) so they get green-lit. These are the unnecessary and often ill-advised redesigns that we see so often.
https://9to5google.com/2018/07/17/google-blob-emoji-gboard-s...
I don't know what theme the OP is using, but the default dark theme's active tab color is noticeably lighter than any other element in the chrome without any changes. EDIT: I see now. They're using one of the custom Firefox Color themes. I haven't really dug into those; usually the default dark theme is good enough for me.
It's easy to navigate, provides more information in some cases (I really like the second line of smaller text indicating things like a video playing or autoplay being blocked), and I don't feel like anything of value was lost, just reorganized a bit.
I also prefer the Container color bars at the top than at the bottom where they used to be as it gives them more prominence. The only thing I would probably change is I prefer the "+" button to be static on the right hand side. But that's minor and if I truly cared enough, probably super easy to fix in the userChrome.css.
Note: This is mostly on macOS, which is what I spend most of the day running at work. My experience on my Windows PC at home has been mostly the same, though.
Firefox needs to figure out how to expose UI customization to all users, not only those who are comfortable enabling user styles and hacking CSS. Most UI styles probably are using CSS variables, so how about starting to expose them in some easy to use interface, with simple textbox or spinner? Of course, they should plop a huge banner, that customizations are not supported, but in the end this should help users to quickly fix their personal annoyances. It is impossible to make single UI that will satisfy all users, but such customization tool surely will turn more grumpy users to happy users. Imagine, how disabled person must feel, when they need to go through 10 steps of browser customization just to adjust a single color.
More advanced customization is obviously harder to put in to a UI, but exposing the underlying CSS means that anyone can just copy from a blog post like this fairly easily. That seems like a decent compromise to me. I certainly don't recall being able to edit any pre-CSS application with that level of refinement.
I liked the old philosophy that a desktop should have "consistent look & feel". If all your apps use the same UI toolkit, that toolkit can be made to work well and with things like accessibility in mind, and can be themed/customized to the user's preference.
My old-hat way of thinking goes so far to say that "tabs" should be done by the window-manager, not the browser.
1. Visit about:config
2. Set browser.proton.enabled to: false
3. Set browser.uidensity to: 1
4. Optionally, set browser.proton.toolbar.version to: 3
No userChrome.css edits necessary.
We can only hope, anyways.
The first day 89 was out, I got a call from a user wondering what the heck happened to Firefox, and if I did something.
I haven’t gotten used to it yet, but oh well.
Edit: Apparently you need to set custom CSS for this. You might need to enable Expert Options at the top of the preferences screen. I've got:
.tab.active {
background-color: #371737;
}
.tab:hover {
background-color: #600;
}
These colors are I think slightly more obvious than the default was; just toy with the values a little (lower is less color / darker and vice versa). Not sure if this part of my CSS is also relevant / needed to work well with these colors: #tabbar {
background-color: #000;
}
.tab {
background-color: #171717;
}I liked the tree style tabs but didn't want to have two components basically doing the same thing taking up my screen space. I don't know if there was a way to hide the regular tabs.
I have TST enabled with the "regular" tab bar disabled, and can very much still see/use the window buttons.
#TabsToolbar {
visibility: collapse;
}
#titlebar {
visibility: collapse;
}
and the result: #main-window[tabsintitlebar="true"]:not([extradragspace="true"]) #TabsToolbar > .toolbar-items {
opacity: 0;
pointer-events: none;
}
#main-window:not([tabsintitlebar="true"]) #TabsToolbar {
visibility: collapse !important;
}
#sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"] #sidebar-header {
display: none;
}
It's probably worth noting that I've also set "browser.tabs.drawInTitlebar" option to "false" in about:config.Then click the "title bar" checkbox at the bottom left.
https://gist.github.com/drcharris/0830ff4da063c68b0ceed415d8...
/* Hide tab bar in FF Quantum */
@-moz-document url("chrome://browser/content/browser.xhtml") {
#TabsToolbar {
visibility: collapse !important;
margin-bottom: 21px !important;
}
#sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"] #sidebar-header {
visibility: collapse !important;
}
}
I think I probably got it from here: https://www.reddit.com/r/FirefoxCSS/comments/d4hx49/ff69/Edit: More authoritative source shared in the comments which is probably a better starting point (and has loads of other configuration too): https://github.com/piroor/treestyletab/wiki/Code-snippets-fo...
(It does seem to hide the min/max buttons on the left, but I don't use those anyways)
https://github.com/piroor/treestyletab/wiki/Code-snippets-fo...
/*Collapse in default state and add transition*/
#sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"] {
overflow: hidden;
min-width: 40px;
max-width: 40px;
transition: all 0.2s ease;
border-right: 1px solid #0c0c0d;
position: absolute;
left: 0px;
z-index: 20;
}
/*Expand to 260px on hover*/
#sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"]:hover,
#sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"] #sidebar {
min-width: 260px !important;
max-width: 260px !important;
margin-right: -220px;
}
#sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"] + #sidebar-splitter {
display: none;
}
#sidebar-box[sidebarcommand="treestyletab_piro_sakura_ne_jp-sidebar-action"] > #sidebar-header {
visibility: collapse;
}
/* hides the native tabs */
#TabsToolbar {
visibility: collapse;
}
#titlebar {
visibility: collapse;
}
This provides the benefits of tree-style tabs without constantly taking up horizontal space.[0]: https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
Set browser.proton.enabled to false in about:config. That makes Firefox 89 use the Windows 10 accent color in the titlebar again on my system.
.tabbrowser-tab[selected] {
background: #fcb731 ! important;
}
Already makes the active tab visibility so much clearer.I just did a check, they use #FFFFFF for active tab and #F0F0F0 for non active tab.
Using https://webaim.org/resources/contrastchecker/
Gives a contrast ratio of 1.13:1
A big fat fail
I was waiting for some days of use to make my opinion. My _personal_ experience was great! All feels more cohesive and friendly.
And seeing all the styles and components making sense together, I think that this is the start of a good direction. Is a measured refresh, not a change of paradigm or something like that, a good decision of the design team.
I understand the backlash that UI changes has on users, sometimes is justified, sometimes is Old Man Yells at Cloud.
This new look and experience is also good to compete with Chrome and Edge, a design that works well but _also_ looks attractive for the times, is a way to get new users.
Good work Firefox team!
Also I know some people are mad the menus are too tall.
ProTip don't try to disable the new "proton" menus its all whacky.
I swear the "PLAYING" text wasn't there when I first updated. Seems like maybe they're still ironing out how to handle it.
If anyone knows how to turn this off, or prevent it moving the tab title up and down please let me know.
Pausing a video in one window then a second later having my attention drawn back to it by the movement is very annoying. I'm on xubuntu.
These constant changes are preposterous. And not just Firefox, everything.
While we're at it, could one get a classic-ish Windows control panel and dialogs back, in the manner of the Classic Shell/Start menu?
Please? Pretty please? With a cherry on top?
/\* Make the tabs not blend into the background \*/
.tabbrowser-tab:not([selected]) .tab-content {
background: #58506040;
border-radius: 4px 4px 4px 4px !important;
margin-bottom: 4px !important;
margin-top: 4px !important;
}
Setting transparency on the background element doesn't cover up the container color. .tab-content {
background: #ffffff20 !important;
border-radius: 4px 4px 4px 4px !important;
margin-bottom: 4px !important;
margin-top: 4px !important;
}As I frequently mouse between the browser content window and tabs it just seems to be more efficient IMHO.
Perhaps they've added back the option for tabs on the bottom, but it inexplicably vanished many versions ago.
You should be able to independently drag tabs around to any edge of the window you prefer: top, bottom, left or right.
So, for example, you can lay out your many source code tabs along the right, so they stack vertically and you can read all their titles, and lay out your several shell tabs along the bottom, where they're easy to find. Or whatever you want!
Tabbed windows:
https://en.wikipedia.org/wiki/Tab_(interface)
>Large numbers of tabbed windows scale better with the tabs along the left or right edges of the window, instead of the top or bottom edges. That is because tab labels are usually much wider than they are tall, and because it is now common to use displays which are considerably wider than needed for displaying documents and web pages. The NeWS version of the UniPress Emacs text editor placed tabs along the right window edge, and laid windows out in a vertical column, so each tab was initially visible, and the user could use them to raise and lower the windows, drag them around in the column, or pull them out to anywhere on the screen.
>Tabbed window interfaces can give the user the freedom to position the tabs along any edge, so all four edges are available to organize different groups of tabs as the user or application sees fit. The PSIBER visual PostScript programming environment for NeWS had tabbed views that the user could stick onto the stack (represented as a "spike"), and the user could move the tabs to any edge.[3] The NeWS pie menu and tab window manager enabled users to position the tabs anywhere along any edge, and the tabs popped up pie menus with window management functions, to uncover and bury windows, etc.
Emacs with tabbed windows and the HyperTies hypermedia browser:
https://en.wikipedia.org/wiki/Tab_(interface)#/media/File:Hy...
PSIBER Space Deck visual PostScript debugging environment with tabbed object windows that you can impale on the PostScript stack "spike":
https://en.wikipedia.org/wiki/Tab_(interface)#/media/File:Ps...
The Shape of PSIBER Space, Tabbed Windows:
https://donhopkins.medium.com/the-shape-of-psiber-space-octo...
>Tab Windows: The objects on the deck are displayed in windows with labeled tabs sticking out of them, showing the data type of the object. You can move an object around by grabbing its tab with the mouse and dragging it. You can perform direct stack manipulation, pushing it onto stack by dragging its tab onto the spike, and changing its place on the stack by dragging it up and down the spike. It implements a mutant form of “Snap-dragging”, that constrains non-vertical movement when an object is snapped onto the stack, but allows you to pop it off by pulling it far enough away or lifting it off the top. [Bier, Snap-dragging] The menu that pops up over the tab lets you do things to the whole window, like changing view characteristics, moving the tab around, repainting or recomputing the layout, and printing the view.
Tabbed windows for The NeWS Toolkit 3.0 / OpenWindows 3:
https://www.donhopkins.com/home/archive/NeWS/tab-3.0.2.ps.tx...
NeWS Tab Window Demo:
- I changed the "button" to be a simple rectangle the entire height of the tab-bar.
- I removed extra space between the pinned tabs and the regular tabs.
I think the old Chromium's fonts are so much nicer, I get a lot less eye strain reading long documents with it. Regular up-to-date Google Chrome looks the same as Firefox to me, both fonts are too thick. I've messed around with font settings but haven't been able to find anything that makes them look as crisp as Chromium does.
I think allowing customization of the UI is a great feature set to provide, and it aligns quite well with the imagine Mozilla has set up for itself as an organization. Though, I can see how the teams behind these decisions would want to stray away from having their 'product identity' be something you can easily turn off.
Visit about:config and update browser.tabs.tabMinWidth to 100 or 110, whichever looks better to you.
[^1]: https://addons.mozilla.org/en-GB/firefox/addon/tree-style-ta...
Also I would also like to know the reason behind on this new tab design. What was it trying to solve that was a problem before ? More of a curious question
Every time I have to use either Chrome or a recent version of Firefox(or any version with default settings, really) it's a terribly frustrating experience.
Though I must admit, I am utterly baffled at their decision to turn tabs into buttons visually, though the behavior is the same.
Tabs are now a universally understood UI element, as common as checkboxes or menus or folders. This is like... deciding to make checkboxes round instead of square, so now they're confused with radio buttons.
What possible reason did the Mozilla UI team have for deciding to make tabs... look like buttons?
They changed the style of the tabs. That's it. People really can act like spoiled children sometimes, it's ridiculous.
It's not a disaster, lots of less vocal people love how it looks now. I love it.
It's a little more work, but it's doable. It's been stable and surviving updates without needing maintenance for many months now.