4 ms·
Sounds to me like focusing on the slight shift in tab location, as pioneered by Chrome, is exactly the kind of nitpicking you're complaining about. It's not lik
by hetman 13y ago
Sounds to me like focusing on the slight shift in tab location, as pioneered by Chrome, is exactly the kind of nitpicking you're complaining about. It's not like moving the tabs up a couple pixels fundamentally changed the browser.
When Opera first pioneered tabs they were found on the bottom. It was Firefox that made the drastic (though unsurprising) change of moving them above the page contents. One could argue maybe Chrome should not have employed this "tired" design choice and perhaps placed their tabs on the left (a la Ubuntu Unity). But this whole line of argumentation sounds ridiculous when someone has already figured out a pretty optimal place for those tabs.
- V-2 13y agoIt's not just any "couple of pixels" that can make a crucial difference in the UX. It's not about the number of pixels, it's about moving the tab bar to the edge of the screen that matters. See http://www.codinghorror.com/blog/2006/08/fitts-law-and-infinite-width.html http://www.codinghorror.com/blog/2006/08/fitts-law-and-infin... Yes obviously Google was not the first one to put that principle to some use, but their browser was the first one among web browsers. Personally I hated how Opera left a few pixels gap between the tabs and the screen edge (I have no idea if they still do). A few pixels was just enough to make sure that I had to move the mouse cursor a little bit back every time I wanted to click on a tab.