Dave Tapuska
Dave Tapuska
You should retest this on Chrome 72, rAF now works correctly due to redesign of user activation
Adding back the hierachy restrictions for this event targetting is unforunate. We are forcing users into a model of how to design their application that the content must be present...
I've posted my proposal here: https://github.com/dtapuska/useractivation TLDR: add navigator.userActivation and message.userActivation
@dotproto ping, PTAL
Seems dragula has some bindings for pointerevents. And those really are the preferred approach albeit I don't know if your use case works correctly with pointer events because perhaps it...
That code looks like it will break for Opera when they move up to version 61 of blink. Not good.
Why not change this to be based on document.scrollingElement instead? Something like: target: (document.scrollingElement ? document.scrollingElement : $('body')), Then you can avoid the user agent checks.
So the document.scrollingElement was added and it provides a quick selection of what scrolling element is (can be document or body depending on what mode the document is in). Basically...
I think self.target in fact is wrong.. and it really should be document.scrollingElement but I'm not a javascript wizard at all. Perhaps @simov can comment.
Perhaps EventTarget.supportsEventListenerOptions should actually be used no? There are some cases where you'd like to test whether something supports passive or not. But I think the bulk of the concern...