- From: <bugzilla@jessica.w3.org>
- Date: Sun, 11 May 2014 18:36:00 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25657 Bug ID: 25657 Summary: [D3E] click event after mousedown and mouseup events (more detail) Product: WebAppsWG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: DOM3 Events Assignee: travil@microsoft.com Reporter: crimsteam@gmail.com QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, www-dom@w3.org D3E is the only specification where this behavior is described? If yes then definition should be more accurate. Now we have only this: "Each implementation will determine the appropriate hysteresis tolerance, but in general SHOULD fire click and dblclick events when the event target of the associated mousedown and mouseup events is the same element with no mouseout or mouseleave events intervening, and SHOULD fire click and dblclick events on the nearest common ancestor when the event targets of the associated mousedown and mouseup events are different." But ancestor for which target (mousedown, mouseup or both)? When both what if we have mousedown on <body> and mouseup on <html>? What target will be set? Mayebe use term sth like this: nearest common "inclusive ancestor" (http://www.w3.org/TR/dom/#concept-tree-inclusive-ancestor) will be better. Just only suggest to add more details because now we have different behaviors in browsers: https://bugzilla.mozilla.org/show_bug.cgi?id=1004895 -- You are receiving this mail because: You are on the CC list for the bug.
Received on Sunday, 11 May 2014 18:36:01 UTC