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 Feb 11, 2021. It is now read-only.
I'm running into an error with touch to pointerEvents, where pointer up's are not being generated if the content being touched changes after the touch has started. Moreover Polymer sometimes crashes with the error message: "Object # has no method 'elementFromPoint'"
I've been looking at this bug just now, and I think the main issue is that the targetFinding code for the touches can accidentally return an element instead of Document or ShadowRoot if the element gets disconnected from the DOM.
This issue only seems to manifest in the ShadowDOM Polyfill probably due to some quirk in the overriding of parentNode. Making sure a valid root is returned from this.owner seems to fix this.
I'm running into an error with touch to pointerEvents, where pointer up's are not being generated if the content being touched changes after the touch has started. Moreover Polymer sometimes crashes with the error message: "Object # has no method 'elementFromPoint'"
Device info:
Chromebook Pixel
Browser: Chromium 33.0.1735.0 (Developer Build 239803)
For an example where the error message consistently appears:
For the missing pounterUp event:
Expected output:
touch
mode a:down
touch
mode b:up
Actual ouput:
touch
mode a:down
The text was updated successfully, but these errors were encountered: