You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2018. It is now read-only.
Like #38, another library useful for easy adoption would be to expose a new set of events: touchstarted and touchmoved (like the API discussed in #24) or aftertouchstart and aftertouchmove. These would be implemented on top of passive touch listeners (perhaps via a setTimeout(0)). This would have the advantage of making it easy for script consuming DOM events via various frameworks (like jquery/jquery#2871) to opt-in to using passive touch listeners.
Thoughts?
The text was updated successfully, but these errors were encountered:
Of course an obvious downside of this approach is that it doubles the event dispatch costs, which in the case of touchmove can sometimes add up to a non-trivial fraction of the frame budget.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Like #38, another library useful for easy adoption would be to expose a new set of events:
touchstarted
andtouchmoved
(like the API discussed in #24) oraftertouchstart
andaftertouchmove
. These would be implemented on top of passive touch listeners (perhaps via asetTimeout(0)
). This would have the advantage of making it easy for script consuming DOM events via various frameworks (like jquery/jquery#2871) to opt-in to using passive touch listeners.Thoughts?
The text was updated successfully, but these errors were encountered: