New issue
Advanced search Search tips

Issue 764250 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

When you use the stylus, mouseup event is no longer fired after the input elements with type="file" is selected

Reported by lingyi...@gmail.com, Sep 12 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
I added a mouseup event to a button, start using the stylus to click on it, it can be triggered.

But if you select a file, and then click the button with stylus, mouseup event is no longer trigger again. 

PS: If you do not use the stylus but click with your fingers, it is no problem.

What is the expected behavior?

What went wrong?
The mouseup event is no longer fired again.

Did this work before? Yes 57 

Chrome version: 60.0.3112.90  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 26.0 r0

See https://codepen.io/lingyired/pen/ZXzQvy for a demo of the issue.
 
mouseup -bug.gif
282 KB View Download
Labels: -Arch-x86_64 -Via-Wizard-Javascript Hotlist-Input-Dev
Owner: dtapu...@chromium.org
I can reproduce at Surface Pro, stable and canary channel. Also update the test code.
https://codepen.io/anon/pen/VMwLEL?editors=1111
Components: -Blink Blink>Input
Labels: Needs-Bisect Needs-Triage-M60
We can check whether this is a regression from #2 testcase.

Comment 5 by ajha@chromium.org, Sep 13 2017

Labels: TE-NeedsTriageFromMTV
This requires stylus to test and confirm the behavior. Tested this on Windows-10 touchlaptop on the latest canary(63.0.3213.0) but this seems to be working fine with finger and "mouseup" event if fired every time on clicking the button. Tested with https://codepen.io/anon/pen/VMwLEL?editors=1111 as per C#2. 

Looping MTV team to check this from their end as well.
Status: Fixed (was: Unconfirmed)
This is working correctly in Chrome Canary. Likely was related to stylus changes making it work more like touch.

Sign in to add a comment