|
|
|
|
|
by jehlakj
1845 days ago
|
|
That’s pretty neat, but it doesn’t justify their UX decisions. Why change something that seemed to work well? Do they have constant feedback on their previous design? 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.