New issue
Advanced search Search tips

Issue 619295 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature


Participants' hotlists:
Fixing-touch


Sign in to add a comment

Touch Input behaves differently to touchpad input

Reported by razgriz....@gmail.com, Jun 11 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8172.47.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36
Platform: 8172.47.0 (Official Build) stable-channel cyan

Steps to reproduce the problem:
1. Use touchscreen to drag and drop on web elements
2. Use touchscreen to highlight words in Google Docs
3. General use of touchscreen

What is the expected behavior?
1. When dragging and dropping files, the target webapp/webpage should be able to detect the file that has been dropped
2. When using Google Docs, double tapping a word should highlight it, a further tap selects the whole paragragh, and the user should be free to go through menus whilst the text is selected
3. Single tap for single click, long tap for right click/drag

What went wrong?
1. Elements are not accepted, when using touchpad, the file is accepted by the target webapp/webpage
2. It is extremely difficult to select a single word, and when selected, as soon as you interact with the font/style menus, the selection is lost. 
3. Very often, a single tap will be registered as a long tap

Did this work before? No 

Chrome version: 51.0.2704.79  Channel: stable
OS Version: 8172.47.0
Flash Version: Shockwave Flash 21.0 r0

It appears that touch is not giving the same fuctionality as using a touchpad and keyboard, often having to revert back to using the R11 in laptop form means that the touch input is far from perfect and needs some tweaks. I'm not entirely sure why ChromeOS differentiates a drag and drop with touchscreen to a drag and drop with the touchpad.
 
Cc: kathrelk...@chromium.org
Components: UI>Touch Internals>Input>Touch>Pad
Cc: -kathrelk...@chromium.org tbuck...@chromium.org wjmaclean@chromium.org rbyers@chromium.org
Components: -Internals>Input>Touch>Pad Internals>Input>Touch>Screen
Status: Untriaged (was: Unconfirmed)
Labels: -Type-Bug Type-Feature
Status: WontFix (was: Untriaged)
1. Is not reproducible
2. Is a feature request but marking as won't fix - working as intended for touch interaction
Components: UI>Shell>TouchView
Components: -UI>Touch
Project Member

Comment 6 by bugdroid1@chromium.org, Sep 22 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fe97880e4c15a1faef6b25570f023ecb0955fe41

commit fe97880e4c15a1faef6b25570f023ecb0955fe41
Author: Steven Bennetts <stevenjb@chromium.org>
Date: Fri Sep 22 03:43:31 2017

Settings: Display: Orientation disable merge fix

Bug:  619295 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I598f3f1fa39e93c5b252f831d7d59c189e91feee
Reviewed-on: https://chromium-review.googlesource.com/677886
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#503635}
[modify] https://crrev.com/fe97880e4c15a1faef6b25570f023ecb0955fe41/chrome/browser/resources/settings/device_page/display.html

Sign in to add a comment