Issue metadata
Sign in to add a comment
|
Disable Chrome's two-finger back/forward navigation on OSX by default
Reported by
rou...@gmail.com,
Jun 21 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 Steps to reproduce the problem: This usability issue has been discussed ad nauseam on stack exchange with hundreds of thousands of views: https://apple.stackexchange.com/questions/21236/how-do-i-disable-chromes-two-finger-back-forward-navigation# To reproduce: 1. Open a page 2. Go to another page 3. Use two fingers to navigate back, and you will go back to the first page. The detection of the two finger swipe is so sensitive on macs that this gets triggered very easily. What is the expected behavior? The expected behavior is to design a UX that doesn't cause end users to inadvertently end up going back one page. This is a huge productivity killer. Take a cue from applications that have implemented this feature much better such as Safari. What went wrong? End users are inadvertently going back one page. This is a huge productivity killer. Did this work before? N/A Chrome version: 67.0.3396.87 Channel: stable OS Version: OS X 10.13.2 Flash Version: Shockwave Flash 30.0 r0
,
Jun 21 2018
rouble@ Thanks for the issue. As per the above description, this is a feature request to disable Chrome's two finger back/forward navigation on Mac OS. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Jun 30 2018
[chrome mac triage] Assigning to ellyjones@
,
Jul 2
,
Jul 6
The NextAction date has arrived: 2018-07-06
,
Jul 6
Okay - I thought some more about this. I actually have the opposite problem, namely that I can't reliably trigger two-finger navigation when I want to. I think perhaps this logic here: <https://cs.chromium.org/chromium/src/chrome/browser/renderer_host/chrome_render_widget_host_view_mac_history_swiper.mm?type=cs&g=0&l=564> needs some thought and perhaps rework. I see a TODO for erikchen@ to reconsider the logic there already, so I'm assigning this to erikchen@, but let's not target M69 here.
,
Jul 9
The initial request by the user was to implement a Safari-style slide the whole page to reveal the page underneath, not to get rid of the feature. Given that this feature has been present for many years, I don't think we should get rid of it because of a single user request for a change in behavior. At the very least, we should be coordinating more closely with UX. Back to Elly.
,
Jul 9
Aha, okay. I'll put this on my list of Things To Investigate Later.
,
Jul 9
Thanks for looking into this. I agree with what Eric has said, but I just wanted to add, this is not something that a single user has requested. This is one of the most popular questions on apple stackexchange with over 130K views: https://apple.stackexchange.com/questions/21236/how-do-i-disable-chromes-two-finger-back-forward-navigation# I am a tech lead in software engineering, and most people I know disable this "feature" as soon as they get a new mac. There is definitely a high priority UX issue here.
,
Sep 1
The NextAction date has arrived: 2018-09-01
,
Sep 4
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Jun 21 2018