Recommended Posts

yeah and not to mention the very distinct "keyhole" design.

and chrome's UI looks like it's from the windows xp luna days rather then windows 7/2008 aero or mac osx aqua era

Just more and more ridicolous. Among all the things firefox could have copied from chrome, they took its fugly UI. very well done

To be fair it looked like that in all versions of Firefox before Firefox 4. Firefox 3 had "native" buttons with some custom back-forward ones with the keyhole design.

I prefer "native" to system design anyday. see the bug for some example I provided. if you don't wanna dig through the mess compare openoffice ('system' styled) to anything like IE9/windows live essentials, Fx, WMP, etc.....

I prefer "native" to system design anyday. see the bug for some example I provided. if you don't wanna dig through the mess compare openoffice to anything like IE9/windows live essentials, Fx, WMP, etc.....

Not sure what the correct term even is, but all previous versions of Firefox had that button design. I'm not sure why they would waste so much time designing and implementing all these new designs just to revert back to the old days.

Nothing in Vista/7 even uses this button design so it is really odd.

Don't worry Mozilla is making Firefox ugly in an attempt to get Chrome users back.

LOL.

To be honest though, I've always found Firefox to be somewhat ugly up until Fx4, and even then it was just okay.

Even though I don't care for the resemblance to Chrome I'm just glad they're putting more resources into the UI other than just mockups.

Some people swear blind that IE9 is the prettiest, some say Opera ... to a reasonable extent UI and UX is a personal preference. Personally, I've already applied a stylish to remove button backgrounds (except on hover), because I fail to see the need for them. It's just extra lines.

Just because Chrome does something isn't a reason *not* to do it. Following others blindly is never a good approach, but this is not evidence of that.

Also, the UX build is a testing ground, not a *if it's in here, it'll be in a future release (unchanged, or even at all)*.

Some people swear blind that IE9 is the prettiest, some say Opera ... to a reasonable extent UI and UX is a personal preference. Personally, I've already applied a stylish to remove button backgrounds (except on hover), because I fail to see the need for them. It's just extra lines.

Just because Chrome does something isn't a reason *not* to do it. Following others blindly is never a good approach, but this is not evidence of that.

Also, the UX build is a testing ground, not a *if it's in here, it'll be in a future release (at all, or just unchanged)*.

Some people fail to realize that Chrome didn't invent borderless buttons.

Not sure if you're implying I think they did? Cause that's certainly not what I'm implying, nor would it matter. (But it's a fair point at anyone who thinks they did).

That's not what I meant. I was simply agreeing with you in a way, I probably shouldn't have quoted. It seems a lot of people complain that Mozilla is using borderless buttons. All version of Firefox prior to Firefox 4 had them, then they got changed in Firefox 4, now apparently they want them back. I've read so many complaints that Firefox is copying Chrome in this aspect, but it simply isn't the case.

I dont like the curved tabs either but the last screenshot on that website I think is REALLY sharp.

But mockups... We all know what happens with them. So many things were trashed for Fx4, including some things that actually made it in the nightlies.

I wish they would come up with one decent design and stick with it, at least for a year.

http://people.mozilla.com/~shorlander/ux-presentation/ux-presentation.html does look interesting.

With the massive caveat that they are mockups, and that doesn't mean Firefox will look like that ... the full screen views make a lot of sense, and the OSX menu design is fairly novel. Not sure about the 'flowing' tabs, but just because Chrome has them doesn't mean they're a bad design. Certainly to many they are more attractive than box tabs.

But mockups... We all know what happens with them. So many things were trashed for Fx4, including some things that actually made it in the nightlies.

I wish they would come up with one decent design and stick with it, at least for a year.

Product design just doesn't work like that, unfortunately. You find issues during implementation, or you find a better way to do something, or time constraints prevent you from coding it. It would be *nice*, and often the closer you can stick to mockups, the better, but it's rare to stick to a design over the course of several months of coding (especially in a rapidly changing market).

And indeed, with regular code releases, it doesn't often make sense to hold back new UI work just so you can do it all at once (for one, that would likely be a development nightmare).

^I understand changes are needed when it goes from mockups to actual implementation but at the moment it seems they're changing the design depending on their mood and they're not small changes so it can be implemented properly, either.

From the 4.0 mockups to the final release of Fx4 I thought they did a pretty good job of implementing what they set out to do and they're already scrapping most of it which I think is a shame.

^I understand changes are needed when it goes from mockups to actual implementation but at the moment it seems they're changing the design depending on their mood and they're not small changes so it can be implemented properly, either.

From the 4.0 mockups to the final release of Fx4 I thought they did a pretty good job of implementing what they set out to do and they're already scrapping most of it which I think is a shame.

I wouldn't say they are 'scrapping' it, really - tweaking and refining it, more like. Design work is a lot of iteration, and to have gone from Fx 3.6 to the new design seen above would be far too disruptive to the code and user experiences - so what happens are steps on a long road. Fx4 did make a variety of very good changes to the UI, but even Fx4's original designs were somewhat more radical than we got (e.g. no home tab yet, and other stuff on http://areweprettyyet.com).

In any case, yeah I agree that it would be nice to settle on a single design for a long period of time ... but it'll never happen, and rarely happens in any software, especially not browsers. (I would argue Firefox's previous feeling of more stable design was born more out of slow release schedules, than intent.)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? Sure, the way Microsoft is pushing 'Microsoft Edge' on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!