New issue
Advanced search Search tips

Issue 792795 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

dragover consumes external drag-and-drop event

Reported by kha...@gmail.com, Dec 7 2017

Issue description

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

Steps to reproduce the problem:
So this is continuing from https://bugzilla.mozilla.org/show_bug.cgi?id=1417276#c1, since they claim it's not a Firefox bug. I suspect it's somewhere in between. 
1. Open this in chrome/ium/electron
<!DOCTYPE html>
<html>
<head>
    <script type="text/javascript">
        window.onload = function() {

            var body = document.getElementsByTagName("html")[0];
            body.addEventListener("dragover", function(event) {
                event.preventDefault();
            }, false);
        };
    </script>
</head>
<body>
</body>
</html>
2. Open a firefox browser with two tabs
3. Drag one of the tabs onto the open chrome web page
4. Notice that firefox does not open a tab at the mouse cursor.

2-4 also work with Microsoft Edge, which I assume has a similar style for tab detaching as firefox, although edge opens the tab on the wrong screen, rather than not at all.

Compare to dragging over other web pages that don't bind dragover and preventDefault.

Chrome itself is not affected, since it has a different style of moving tabs.

What is the expected behavior?
Firefox/Edge pops open a new tab at cursor

What went wrong?
Firefox does nothing/Edge opens in different place.

Did this work before? N/A 

Chrome version: 62.0.3202.94  Channel: n/a
OS Version: 10.0
Flash Version:
 
Status: Archived (was: Unconfirmed)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment