New tab button position should be fixed on macOS and iPad
Reported by
billdill...@gmail.com,
Nov 16
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: Safari for macOS and iPad have a fixed position new tab button. When a user that is used to Safari tries Chrome, the moving new tab button is enough of a step back that they are likely to go back to Safari. What is the expected behavior? What went wrong? Users of Safari on macOS and iPad (and there are many) are used to a fixed position new tab button, Chrome should not go against this because there is no benefit to having a moving new tab button, but also, it's actually a step back for these users (the new tab button is a moving target). It has surely cost us macOS and iPad users, and if it is not changed, it will continue to cost us users. At the very least, macOS and iPad users should be given the option to have a fixed position new tab button. Did this work before? N/A Chrome version: 70.0.3538.102 Channel: stable OS Version: 10.14 Flash Version:
,
Nov 16
billdillensrevenge@ Thanks for the issue. As per the above description, this looks like a feature request for chrome to have a fixed position new tab button like Safari on Mac OS. Marking this as Untriaged for further updates from Dev. Thanks..
,
Nov 16
,
Nov 16
-> Assigning to markchang@ according to issue 822063 (c#54 & c#55).
,
Nov 18
Also it's worth noting that Edge for iPad and Firefox for iPad have a fixed position new tab button, Chrome is the only major iPad browser with a moving new tab button...
,
Nov 18
,
Dec 7
,
Dec 7
Assigning to pschaffner@ for UX opinion.
,
Dec 7
Given that this would change design across all platforms, ainslie@ should probably be a decision-maker.
,
Dec 7
Ahh - yes. We've explored (and implemented) fixed-position new tab buttons in the past. But because we currently 1. constrain the width of our tabs and 2. don't use a text label for the new tab button, our usability assessment is that keeping the button next to the "final" tab in the set does a better job communicating its "create-more-of-these-things" function. And we acknowledge the fixed position tradeoff.
,
Dec 7
Understood but I did just want to note that, once you have enough tabs open (and this is extremely common), the new tab button is effectively 'fixed', so it's not a very consistent experience at the moment. Making it fixed position wouldn't harm macOS or iPad users and this should at least be optional for them |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Nov 16