Open
Bug 1430812
Opened 6 years ago
Updated 2 years ago
Doubleclick event is handled differently from other browser
Categories
(Core :: DOM: Events, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: mstanke, Unassigned)
Details
Attachments
(1 file)
1.15 KB,
text/html
|
Details |
I have got a report from a developer claiming the behaviour of doubleclick event handling changed in Firefox 57 and is now also different from other browsers. Please see the attachment. When you doubleclick the text in Chrome, IE, Edge and probably Firefox 56 too, the dblClick event is fired (verified myself in Chromium only). In Firefox 57, only single click events happen. My personal understanding of the code is that the behaviour is correct, as during the first click the event with dblClick listener is replaced by another one and there can be no second click on it. However the reporter sees this as Firefox specific behaviour (and wrong). Note: In Chromium the behaviour is really weird to me. The dlbClick event happens on the new element, which did not existed in the DOM at all in time of the first click (see the console log).
Reporter | ||
Updated•6 years ago
|
Status: NEW → UNCONFIRMED
Ever confirmed: false
Comment 1•6 years ago
|
||
This does reproduce in 56, and I tried as far back as 50 and it still behave as it does currently. The browser compat table at MDN[1] doesn't seem to indicate that we implement it. https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondblclick
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•