- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 11:38:43 +0000
- To: public-css-archive@w3.org
https://user-images.githubusercontent.com/93594/205042084-dd6f02b6-3068-4734-bf80-b51bd47ff5a2.mp4 There are three states in terms of what the user sees: - The real DOM - Paused render - The transition pseudos With the real DOM, input goes to the real DOM. With the pseudos, input goes to the document element. I don't think we should add a third behaviour for the paused render case. Throwing input away could cause more of a 'glitch' in the [gesture example](https://twitter.com/jaffathecake/status/1595811562614558720), as dropped events would mean the initial position could be out of sync with actual pointer position. Doing a hit-test on the real DOM seems risky, as elements might be in completely different places. So, I vote that we do the same as in the "transition pseudos" state, and send events to the document element. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7797#issuecomment-1333634700 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 December 2022 11:38:44 UTC