New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 797217 link

Starred by 1 user
Status: Duplicate
Merged: issue 269917
Owner: ----
Closed: Jan 2018
Cc:
dtapu...@chromium.org
█ sc00335...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

mouseup outside of frame does not fire if mousedown calls preventDefault

Reported by dea...@gmail.com, Dec 22 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36

Steps to reproduce the problem:
1. Make page with frame, add mousedown and mouseup listeners
2. Push down the mouse button inside the frame
3. Move mouse pointer outside the frame
4. Release mouse button

What is the expected behavior?
frame event listener catch mouseup event

What went wrong?
mouseup event triggered only if I don't prevent mousedown event

Did this work before? Yes 

Does this work in other browsers? Yes

Chrome version: 63.0.3239.108  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

In the attached test case first iframe only listen events, second iframe also does preventDefault of mousedown event.
So first iframe listener works correctly, but second does not.
chrome-mousedown.zip
1.2 KB Download

Comment 2 by krajshree@chromium.org, Dec 26 2017

Labels: Needs-Triage-M63 Needs-Bisect

Comment 3 by sc00335...@techmahindra.com, Dec 27 2017

Cc: dtapu...@chromium.org sc00335...@techmahindra.com
Components: Blink>Input
Labels: -Needs-Bisect -Type-Bug-Regression Triaged-ET M-65 OS-Linux OS-Mac Type-Bug
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on reported version 63.0.3239.108 and on latest canary 65.0.3304.0 using Windows10, Mac 10.13.1 and Ubuntu 14.04 with attached html file in comment#0. This issue is seen from M50[50.0.2661.0], Hence  considering this issue as Non-regression and marking as Untriaged.

And as per comment#1 this issue seems to be duplicate of issue 269917.

cc'ing @dtapuska for further inputs on this issue.

Thanks!

Comment 4 by nzolghadr@chromium.org, Jan 4 2018

Mergedinto: 269917
Status: Duplicate (was: Untriaged)
I'll reply on the original issue.
►

Sign in to add a comment