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

Issue 799754 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

HTML5 drag-n-drop doesn't work if browser window is created on external screen

Reported by eric.rannaud@gmail.com, Jan 7 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36

Steps to reproduce the problem:
1. Turn off laptop screen, use external screen only: xrandr --output HDMI3 --auto --output eDP1 --off
2. Create a new browser window (Ctrl+N)
3. Turn off external screen, use laptop screen only: xrandr --output eDP1 --auto --output HDMI3 --off
4. In window created at 2, go to http://www.w3schools.com/html/html5_draganddrop.asp
5. Use the example "Drag the W3Schools image into the rectangle" to try and drag-n-drop the image to the rectangle to the right.

What is the expected behavior?
The ondragenter, ondragover, ondrop events should be fired.

What went wrong?
The image move, but none of the ondragenter, ondragover, ondrop events are fired, and the image cannot be successfully dropped.

The window created at step 2 remains unable to use drag-n-drop no matter what screen it is on (and even if I return to using the external screen alone). Other browser windows can use drag-n-drop normally.

Did this work before? Yes Not sure

Does this work in other browsers? Yes

Chrome version: 63.0.3239.108  Channel: n/a
OS Version: Arch
Flash Version: 

I'm posting a new issue for  Issue 562664  (WontFix). While it is a very similar problem, it appears to be a new occurrence of it, under slightly different conditions. 

I started noticing it just yesterday. I use a webapp nearly every day that relies on drag-n-drop and easily reveals this issue. However, I had never used this app with a sequence of internal / external *alone* / internal screen configurations: I would typically use either the internal screen or use internal+external together in a dual display setup.

As far as I can tell, the two cases described in comment #7 of 562664 are behaving fine (as they have since v56).

For completeness: yesterday I also started using Chromium with chrome://flags/#enable-site-per-process Enabled but I have no idea why that would be at all related.
 
Labels: Needs-Triage-M63 Needs-Bisect
Labels: TE-NeedsTriageFromHYD
The issue need a laptop to desktop connector to test the issue as in the related issue https://bugs.chromium.org/p/chromium/issues/detail?id=562664 xrandr calls it HDMI3, it's an external monitor plugged into a laptop.
Hence, forwarding the issue to inhouse team for further triaging of the issue.

Thanks...!!
eric.rannaud@: thanks for the report!  Can you please check if disabling chrome://flags/#enable-site-per-process fixes this issue?
Components: Internals>Sandbox>SiteIsolation
Speculatively adding SiteIsolation label based on the use of chrome://flags/#enable-site-per-process, so that we can check whether this is a site isolation problem.
The bug is still present with chrome://flags/#enable-site-per-process turned OFF, it doesn't appear to be related.
Components: -Internals>Sandbox>SiteIsolation
#5: thanks for checking!
Cc: sandeepkumars@chromium.org
Labels: -TE-NeedsTriageFromHYD TE-NeedsTriageFromMTV
Tested the issue using #64.0.3282.168 on Linux ubuntu 14.04 and couldn't reproduce the issue as per the steps mentioned in comment #0.

@eric.rannaud: Could you please give a try in latest Chrome #64.0.3282.168

Requesting MTV team for further triaging on this issue as Arch flavoured linux machine isn't available in Hyd.

Thanks!!
Status: WontFix (was: Unconfirmed)
We don't have the hardware to investigate this. Sorry!

If you can figure out what we're doing wrong in the code, happy to look into a fix. 

Sign in to add a comment