New issue
Advanced search Search tips

Issue 865948 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 30
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Get rid of reload button on MacBook Pro Touch Bar

Reported by stsh...@gmail.com, Jul 20

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. Fill out a web form on MacBook Pro
2. While trying to type a number, accidentally hit reload / back arrow buttons on oversensitive touch bar instead
3. Lose all your data entered into the form and start over

What is the expected behavior?
Chrome doesn't expose these dangerous buttons by default

What went wrong?
The touch bar is very sensitive, and if you're not a flawless typist causes all sorts of problems when you brush against it. Chrome's attempt to support it causes more more problems than it solves in my case. I also often hit the "search or type URL' button, bookmark button, and new tab button. That's less disruptive, usually, but still a problem.

Did this work before? N/A 

Chrome version: 67.0.3396.99  Channel: stable
OS Version: OS X 10.13.6
Flash Version: 

Until Apple figures out how to reject false positives on the Touch Bar, be more conservative in your default Touch Bar actions. For now I've disabled *everything* on Touch Bar in Chrome.
 
Owner: markchang@chromium.org
Status: Assigned (was: Unconfirmed)
I thought we did this already?

Over to Mark since it's a product question
Labels: Hotlist-PlatformExcellence M-70
I feel like this is a good change to take on. Putting into our platform excellence bug list to get to near M70.
Labels: Proj-MacViews
There's an option to disable the reload (and other potentially fraught Touch Bar actions), but I believe reload in particular should be disabled default. I'm sure people use it some, but for me at least the risks of accidental use are much higher than the benefits of having it available as an option. Touch Bar activation energy is vastly lower than keyboard keypress, so you're much more likely to cause problems with fat-finger mistakes. I'm no fan of the Touch Bar, though, and this is just my suspicion.
Labels: Target-70
Cc: markchang@chromium.org
Owner: ----
Status: Available (was: Assigned)
Components: -UI UI>Browser>Touchbar
Owner: ellyjo...@chromium.org
Status: Assigned (was: Available)
Assigning to ellyjones@ to take a look at the metrics and to decide the future of the TouchBar in Chrome
Labels: Group-Touchbar
Checking the metrics, unfortunately (for the purposes of this bug) Reload is *by far* the most used button on the touchbar, with 38% of all touchbar use. Here's the breakdown:

Reload 38%
Search 24%
Back 18%
New Tab 7%

the other actions are all under 5%. ~60% of touchbar presses are things that will navigate the main frame.

There's around one touchbar main-frame navigation per 100 main-frame navigations we see on Mac (comparing TouchBar.Default.Metrics to Navigation.MainFrameScheme) so I think use can still be described as "low".

markchang@, let's chat about this later today and decide where to go with it.
I wonder what fraction of that button usage is intentional. I hit reload, search, back, and new tab on the Touch Bar on purpose exactly 0 times, but then I'm a keyboard shortcut person (Cmd- R, L, left arrow, T) which I think is somewhat out of the majority.

Turning off all the Touch Bar options in Chrome has made my life much better, though, so the urgency for me is lower now.
Status: WontFix (was: Assigned)
I chatted with markchang@ (mac PM). We've decided that we aren't going to change the default behavior here. If we were designing the touchbar support from scratch, we probably wouldn't have Back or Reload there, but we don't want to break these UI elements for folks who have gotten used to them. As such, this bug is WontFix.

Sign in to add a comment