- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Apr 2021 19:43:30 +0000
- To: public-pointer-events@w3.org
yeah i'll admit that to me this would feel like a step back, philosophically - as we're trying to get devs to think in more device/input agnostic ways first and foremost. and if they *want* to handle events differently, it doesn't seem to onerous for them to switch/case when they get a pointer event to then have different behaviour at that point. also *if* new classes/types of pointer become popular in future, we'd then need to reinvent further companion events again (e.g. the mentioned eraser, or microsoft dial, as pointers ... it'd be trivial currently to just extend the type values to allow for these, but then magicking up eraserdown/eraserup/etc seems exactly the sort of thing we wanted to avoid by having a generic input-agnostic model) -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/359#issuecomment-819784788 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 April 2021 19:43:32 UTC