New issue
Advanced search Search tips

Issue 695699 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 730232



Sign in to add a comment

File manager: must hit Delete several times using touch

Project Member Reported by kathrelk...@chromium.org, Feb 24 2017

Issue description

From partner, originally reported in crosbug.com/61988

I was able to reproduce this on M57 link using the repro steps provided:


Chrome OS Version  :  9142.0.0
Type of hardware   :  <unreleased device>

Please specify Area-* of the system to which this bug/feature applies (add
the label below).
Cr-OS-Kernel-{Touch Screen}
What steps will reproduce the problem?
1.Updated Rev6 image via recovery media,went to OOBE and boot into OS. 
2.Launched Files from Apps,long pressed blank area to created a new folder. 
3.Used one finger long pressed this new folder and shortcut menu would be popped up. 
4.Chose Delete option from shortcut menu. 
5.Used one finger to touch "DELETE" button form "Are you sure you want to delete "New Folder"?" dialog. 

What is the expected output?
Should be touch "DELETE" once and can delete files successfully.

What do you see instead?
Found it need touch "DELETE" button several times to delete files successfully.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

What is the impact to the user, and is there a workaround? If so, what is
it?
User will consider the touch screen function is broken

Please provide any additional information below.
Can't duplicate this issue via touchpad or mouse.

 
Cc: weifangsun@chromium.org fukino@chromium.org
I wonder if it is similar to this:
https://bugs.chromium.org/p/chromium/issues/detail?id=526877
Owner: yamaguchi@chromium.org
Status: Assigned (was: Untriaged)
yamaguchi@ - Might be good to investigate this while we're looking into touch interactions.
Blocking: 730232
Status: WontFix (was: Assigned)
It did not reproduce with these environments:
58.0.3029.140 / 9334.72.0 (stable) on Chromebook Pixel 2
61.0.3151.0 / 9692.0.0 dev on Chromebook Pixel
So I think this has already been resolved.

Sign in to add a comment