relocate new tab button when "Chrome Home" is enabled in flags
Reported by
billdill...@gmail.com,
Feb 3 2017
|
|||||||||||
Issue descriptionSteps to reproduce the problem: One of the reasons the URL bar is being moved to the bottom is to make Chrome more usable with one hand, but in the tab view, the new tab buttons location is not ideal for one-handed use. It should be moved over. And if not by default, then it should be moved over if someone has Gboard set to one-handed mode (I guess these controls should shift to either side of the screen depending on if the user has selected left-handed mode or right-handed mode). I've attached a screenshot What is the expected behavior? What went wrong? see above Did this work before? N/A Chrome version: 58 Channel: dev OS Version: 6.0 Flash Version:
,
Feb 10 2017
,
Feb 13 2017
,
Mar 31 2017
I know this isn't priority #1 but I hope no one forgets about this, it would be yet another nice improvement to Chrome Home
,
Mar 31 2017
,
Apr 4 2017
The tricky part with moving things one side or the other is that it can be easier or harder depending on which hand you're holding the phone with. In this case, the option to tap overflow > new tab might make it more useful to keep the new tab button where it is.
,
Apr 4 2017
or put the New Tab button in the middle, like Safari for iPhone. Having it in the middle works for both hands
,
Apr 4 2017
,
Apr 22 2017
I don't mean to annoy anyone, and I know this isn't a high priority but please consider moving the New Tab button to the middle for the Chrome Home tab card screen, having it in the middle is the best choice. I know lots of users would appreciate it being in the middle, especially people that have wider phones. I have a Pixel XL and it's a real thumb stretch (I know I COULD tap the over flow button and "New tab" but that's 2 taps. The New Tab has it's own button on this tab card screen for a reason)
,
Apr 24 2017
Thanks for the feedback. This is feedback we're considering as part of on-going design iterations.
,
Jun 22 2017
,
Aug 2 2017
P3 issues don't need (obsolete) target milestones.
,
Aug 10 2017
,
Dec 21 2017
Please don't forget this one!
,
Feb 15 2018
,
Mar 30 2018
The Chrome Home experiment has ended; closing obsolete bug. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by rsgav...@chromium.org
, Feb 6 2017Labels: -Arch-x86_64 triage-te