- From: Samuel Timbó via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Nov 2020 15:06:48 +0000
- To: public-pointer-events@w3.org
@smaug---- the reason is that pointerover/out bubble so the container element will receive such events every time the pointer has entered/left a descendant, which would not make sense for the simple goal of tracking which pointers are currently visible on the screen. This is particularly problematic (and less performant, depending on the handler logic) when the container has many children/grandchildren/etc. This page demo this behavior: [https://glimmer-separated-spell.glitch.me/](https://glimmer-separated-spell.glitch.me/). -- GitHub Notification of comment by samuelmtimbo Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/285#issuecomment-725475644 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 November 2020 15:06:49 UTC