8 ms·
Does anyone feel that this new UI brings notable improvement? I don't think it is much worse, other than taking some extra vertical space but for the most part
by kevincox 5y ago
Does anyone feel that this new UI brings notable improvement? I don't think it is much worse, other than taking some extra vertical space but for the most part my reaction is "meh". I feel like these resources could have been spent much better in other parts of the browser. Am I missing some reason why this is worth the investment?
- SketchySeaBeast 5y agoI've been using it for a while now with Firefox developer edition and I can't figure out a reason why it was done. Does it give a new look? Sure, but I too don't know if anything was made better because of it.
- nathanaldensr 5y agoMany of these changes are made not to improve some actual user grievance but merely to satisfy designer egos or product managers' needs to remain employed. Simply: it's make-work.
- userbinator 5y agoBecause "designers". I'm absolutely sick of this trend of dumbing-down lowest-common-denominator UI, removing useful features and affordances for learning. Insanely huge buttons, rounded corners everywhere, floating controls in a sea-of-white/blackspace... On the bright side, I believe the UI is still highly customisable so it should be possible to make it look exactly as you want, but it's not exactly straightforward.
- ddek 5y agoI think I'll throw a fit when my 'tabs-on-the-bottom' css inevitably stops working. Why? I don't know. It's not notably better, it's just I like having the top of the content at the top of the screen. But it uses the most legacy of firefox's legacy features, so I can't see it staying around forever.
- nsonha 5y agohey have you tried taskbar at the top? I know you didn't ask for suggestion but I'm guessing the taskbar is why you prefer tabs at the bottom?
- anoncake 5y agoSomeone who went to the trouble of moving the tab bar to the bottom, which AFAIK was never a built in feature, probably also dragged around the taskbar at some point if they use an OS/DE that has one.
- trog 5y agoMy userChrome for tabs on bottom stopped with v89 - can I ask what you're using to get tabs on bottom now?
- deleted 5y ago[deleted]
- userbinator 5y agoI'd like some arguments for why this inane trend of UI is occurring, instead of just downvotes... otherwise the "we'll dumb you down so you can't rebel" theory gains more weight! If there's one thing this fucked-up industry is good at, it's lying and pulling the wool over your eyes so they can herd you where they want.
- nsonha 5y agoyeah honestly I don't understand why they don't just freeze the UI and focus on some privacy incentives, that's what end users care as well as where VC money is.
- leodriesch 5y agoI think the new design is really beautiful. For me that is an improvement and I switched from Edge to Firefox for now. But design is always subjective and I can understand how many people would rather see technical improvements over UI refreshes. But as you can see it brings some users back to Firefox.
- Devid2014 5y agoFor me this new UI is worse as the classic one.
- Vinnl 5y agoThere's more info on tabs now, e.g. when a tab is playing audio. And it apparently was also triggered by observing that people didn't really know they could move tabs around and manipulate them in other ways, which does seem more obvious now that they're "detached" from the content. That said, I won't really notice since I use the Sidebery extension for vertical tabs. But I've got a separate profile running to isolate Spotify and its desire for DRM, and there it's been nice in a small way.
- viraptor 5y ago> more info on tabs now, e.g. when a tab is playing audio. That was present for a few versions now. Playing tabs had the audio icon which could be used to mute/unmute.
- Hamuko 5y agoYeah, not only did the old tab design have an indicator what tab was playing audio, it actually was more helpful since the audio indicator did not take over the favicon. I could clearly see that it was YouTube's favicon next to the speaker icon - now I only see the speaker icon.
- alluro2 5y agoTrue - my only gripe with it is that video icon is in the same place - if I have 5 YouTube tabs, 1 playing, that one with audio icon is very hard to distinguish from the other 4 with video icons. Not sure if video icon is useful to some people at all, especially since it's shown even if video is not actively playing.
- bhandziuk 5y agoHuh, for me the speaker icon doesn't show unless I mouseover the tab. So I can't see which tab is playing at all. And the Muted/un-muted icons are almost identical.
- deleted 5y ago[deleted]
- peteretep 5y agoIt's much better when you use it than when you look at the pictures, imho
- chrnad 5y agoI personally think it's a big improvement over what it was before -- on macOS at least. On macOS, Firefox had always felt a little bit off. Nothing too egregious, but just enough to make it slightly unpleasant (like the non-native context menus). I feel like that has been resolved in this update.
- ivanche 5y agoSince you've already mentioned it - I hear that Firefox has non-native context menus all the time, but for the life of me couldn't tell any difference between "native" and "non-native" context menus. Anybody has any proof/example of this?
- pseudalopex 5y agohttps://news.ycombinator.com/item?id=27273724 https://news.ycombinator.com/item?id=27273724
- Hamuko 5y agoRight-click on a word in Chrome/Safari (or really any other macOS application) and right-click on a word in old Firefox.
- sirn 5y agohttps://files.grid.in.th/vKeXJQ.png https://files.grid.in.th/vKeXJQ.png It looks close, but details and behavior are a bit off. For example: - Firefox context menu does not respect system's dark mode - Different horizontal and vertical margins between items - Different font rendering (e.g. text looks bolder) - Different right caret icon For behavior difference, for example: when navigating sub-menu items, macOS uses cursor velocity and cursor direction to determine if user is trying to go to submenu and immediately dismiss it if user is not. Firefox context menu uses a delay to archive similar effect. (To test this: open a sub-menu in a context menu, then move the cursor up. macOS native menu dismiss immediately, where old Firefox has a small delay before it is dismissed.)
- makecheck 5y ago
- hajile 5y agoThe UI/UX team that works on this likely aren't backend coders. They can either fire the team or put them to use, but reassigning them random C++/Rust tasks probably isn't possible.
- kevincox 5y agoTo be perfectly blunt it doesn't matter what a team is doing. They paid $X million to "design resources" and directed those resources at the redesign featured in this release. Instead they could have paid that to backend, other UX initiatives, the extension team, the privacy team... I understand that you can't swing resources around freely in the short term but you don't have a bunch of designers sitting around by accident. Someone decided that they should hire them.
- pseudalopex 5y agoYou're right the money could be spent elsewhere. But calling people resources is rude to put it mildly.
- kevincox 5y agoI said I was being blunt in the prefix. I definitely agree that we need to think about people, that was a large component of "you can't swing resources around freely". Firing people is not something that I would like to see. The point I was trying to emphasize is that it isn't as if Mozilla just happened to have X people with design skills and Y people with whatever other skills. There was planning to build the teams and planning to pick the projects. So while I agree that you can't just put people on random projects I wanted to point out that Mozilla had a lot of agency in the decisions that lead up to a team working on the redesign, it didn't happen just because they happened to have a bunch of designers available.
- Zababa 5y ago> But calling people resources is rude to put it mildly. I don't think it's considered rude, since "Human Resources" is a widely accepted term.
- addicted 5y agoI found the UI changes on windows, while being fairly minor, being much nicer than what was before. It's added a lot of polish without affecting my workflow in any ways.
- bambax 5y agoCompletely useless, yes. The tabs are now semi-transparent on Windows, which is annoying and doesn't help anything. I guess there's an option somewhere to set opacity to 100% but I'm not ready to spend 30 minutes to hunt it down.
- anoncake 5y agoIf it exists, it's likely buried in about:config, which is guarded by a warning telling you to go away. And eventually it will be removed because no one[1] used it, which proves that the designers were right. [1] Except for some weirdos who disabled telemetry. They're probably so paranoid they believe Mozilla would abuse the studies feature to promote a TV series or something like that.
- weavejester 5y agoMy initial reaction to the beta version was that the UI was much worse, but I decided to give it a chance and spend a few weeks trying to get used to it. Now that I've had time to play with it, I'm even more convinced my initial reaction was correct. But I've also had time to reflect on why, and in my view there are two problems with this new design. Removing visual separators from the tabs makes them much harder to distinguish - the only difference between one tab and the next is a larger horizontal space. In prose, when we want to separate sentences, we don't just use longer spaces; we use other visual indicators like capital letters and full stops (periods). Paragraphs are separated by vertical space, which is visually distinct from a horizontal one. The second problem is that the tab you're not supposed to click on (the active tab) looks like a button, while the tabs you are meant to click on (the inactive tabs) are presented as text. This is opposite to normal UX conventions. There are some subjective improvements to the look and feel of this UX change, but overall I'm confused as to why the Firefox UX team would go against established conventions to produce something that's visually more difficult to use and less intuitive than they had before. Fortunately userChrome.css is still usable if you set an about:config option (toolkit.legacyUserProfileCustomizations.stylesheets), so I can see about fixing the problem myself, but I'm concerned that Firefox's march toward reduced configurability will eventually remove this option. Overall, my concerns on Firefox are the same as most; in the pursuit of market share, they're moving further and further away from their roots by removing customisation options. Remember when you could change Firefox's theme without using hidden configuration options?
- tpxl 5y agoOh god, you were not joking. I'm honestly wondering what graphics designers are thinking to come up with a design that _literally will not distinguish neighboring elements from each other_.
- BuckRogers 5y agoPretty good observations. I'm someone who knows very little about UX/UI and what you said makes a lot of sense. Having the active tab "depressed" is more typical. While I think the redesign looks good, I don't really have strong feelings on it. I mostly just want a supported interface, so I finally gave up on compact mode. It's just ok. I guess they wanted to differentiate themselves from Chromium browsers in a more significant way? While most complaints, including from my spouse, are that the tabs are no longer delineated, that part hasn't bothered me much. I consider the delineation the icon on the left, and x on the right. Part of me likes the freshening up. I won't quit using Firefox over these changes, I've been using it for 20 years now and won't be changing until I'm forced. There's still no other browser with a built-in search bar that also works correctly with a keyboard shortcut other than Firefox and Vivaldi. Vivaldi has everything I need in a desktop browser, it just isn't supported at all on iOS which is equally important for me these days. And honestly, Firefox is probably the only browser that isn't from Apple or Microsoft that I'd use. Otherwise I prefer something as important as a browser backed by a truly large organization. Microsoft Edge is really hard to beat in my view once you consider all the intrinsic qualities to it like support. I'll put it this way, no one is making a mistake using Safari or Edge. I like most everything about Firefox, the browser hasn't ever been ruined, but you got to wonder if there's truly even a place for 3rd party browsers in this era. If I weren't a legacy user, I'd just use Edge and be happy not knowing what I'm missing out on with alternatives.
- duped 5y agoThe tabs are more compact than they used to be
- mrweasel 5y agoReally? They seem much bigger, like twice the size. I don’t dislike them as much as I initially did. They’re just a little to big on low resolution monitor. Personally I’d like to see browsers move away from trying to be “special” and just follow the design of operating system. A little tricky on Linux, but for Windows and macOS just follow the guidelines from Microsoft and Apple.
- afranchuk 5y agoI had the same reaction. It reads a bit like the UI engineers didn't have enough to do and stared at it until they found things to change. For instance, having the tab visually disconnected to cue that you can rearrange it is fine... but at this point if a user doesn't know they can rearrange tabs, maybe they shouldn't be rearranging tabs.
- potamic 5y agoI don't like it. The tabs look like buttons and not tabs. It's such an unnecessary deviation from a standard tabbed interface look and feel that everyone is accustomed to. I'm not sure what their reasons are for experimenting with something new but I would be curious to know.
- rhdunn 5y agoI'm using https://github.com/ShatteredIcicle/firefox-ui-regression-mending/blob/master/chrome/photon-tabs.css https://github.com/ShatteredIcicle/firefox-ui-regression-men... in my userChrome.css file to use more traditional looking tabs. I'm trying to figure out how to make the active tab background the same colour as the bar where the forward/backward buttons are so it integrates into that UI.
- herjazz 5y agoI'm using the Lepton fix. That might work for you:- https://github.com/black7375/Firefox-UI-Fix/tree/photon-style https://github.com/black7375/Firefox-UI-Fix/tree/photon-styl...
- open-source-ux 5y ago"I'm not sure what their reasons are for experimenting with something new but I would be curious to know." This is pure speculation on my part, but I assume the "Firefox team" wanted the selected tab to stand out visually. The selected "tab" turns white in the default theme. But if the tab is attached to the URL toolbar, then the URL toolbar also needs to be the same colour as the selected tab. It would look odd if they were attached but each was a different colour. I assume the "Firefox team" wanted the active tab to stand out visually, but not the whole URL toolbar. So the tab becomes a button and is detached from the URL toolbar. Now the active "tab" and the URL toolbar can have different colours: A "louder" colour for the selected tab to make it stand out, and a "quieter" colour for the URL toolbar that lets it recede a little from the foreground. That's what I think may be the reason for the tab change - but as I say, it's pure speculation (and could be completely wrong).
- bambax 5y agoAfter using it for a couple of hours the new version is super annoying. It takes more time and effort to find a tab, everything is less legible. What could possibly be the point of this?? Look more like Chrome? If I want something that looks like Chrome I can use Chrome. It's not like it's more expensive or anything...
- skyfaller 5y agoOne notable recent improvement I will mention is better support for dark mode in the default theme (although I think this fix precedes Firefox 89, it's definitely available in Firefox 88). I previously had to hack the CSS to prevent Firefox pages from searing out my eyes with white at night. These days I'm more satisfied with the default CSS on e.g. the Firefox Home page, although some pages like "view source" still do not respect dark mode unless I edit them.
- jillesvangurp 5y agoI don't mind the changes. I had to look a bit for the new location of the screenshot tool. It's now a button you can add to the toolbar. Otherwise, the changes are mostly pretty subtle and they make sense to me. They have UI people and designers. So they are going to be doing UI and design things. IMHO they are better off with these people than without. Browsers are very competitive. So, keeping the UI fresh and up to date is important. Also, they can't keep everyone happy by changing nothing, which would make yet other people unhappy. So, kind of a damned if you do and damned if you don't. I feel the changes are mostly reasonable and not disruptive so I see very little reason to get upset over these changes.
- sfink 5y agoI had the same issue with the screenshot tool, and added it back, but then I learned that it's been added to the right-click context menu and now I'm torn on whether I still need it as a separate button.
- myfonj 5y agoBesides floating tabs I find rest of Proton overhaul pretty good: better contrast, subjectively nicer colours, better focus styles, nice icons. After removing all corner rounding and tweaking tab bar I am quite happy.
- qmmmur 5y agoCare to share the CSS for removing the rounded corners?
- myfonj 5y agoWell I went full mental and simply bruteforced it [1]. I'm doing it for page content as well with userstyle. [1] https://gist.github.com/myfonj/f5415dd0580663a82ea18407ef2ee5de/#file-_userchrome-css-L50-L58 https://gist.github.com/myfonj/f5415dd0580663a82ea18407ef2ee... This file starts with instructions how to make it work; I'm on Developer edition, Windows, dark theme. Same instruction wit illustration can be seen in Twitter thread [2] [2] https://twitter.com/myfonj/status/1387584962354982912 https://twitter.com/myfonj/status/1387584962354982912