Re: [w3c/uievents] Shall we create a dblclick event when the cursor have moved to a different location between two clicks? (#283)

With the rewrite, the behavior would be specified because it would say something like: generate a dblclick event only if the native OS tells you to.

WRT the sequence of events given above:
(a) It wouldn't really be testing the spec because it wouldn't be injecting native mouse move/click events
(b) However, since it injects events into the middle of the algorithm, the rest of the algorithm should match between UAs

I'm curious about why Firefox apparently synthesizes dblclick events here when they were not provided by the OS. If that is a useful feature, then it should be spec'ed and implemented in all user agents. But as noted above, there are accessibility issues to address as part of that.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/283#issuecomment-738301948