- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 May 2024 13:48:54 +0000
- To: public-pointer-events@w3.org
> I don't think it was just me thinking about having a separate object. [#353 (comment)](https://github.com/w3c/pointerevents/issues/353#issuecomment-1922159406) In fact, based on https://www.w3.org/2024/01/31-pointerevents-minutes.html#t07 it was @flackr who came up with the idea of separate struct :) What wasn't quite captured in the minutes was that I suggested a separate struct as a response to the concern which had been raised prior :-). I'm not sure when it was discussed to find the minutes of. I wanted to find something we could agree on. > And conceptually the new ID isn't about the event but about the device. To clarify, the "device" in this context is the pen, not the touchscreen "device" which itself can sense multiple different pen's each having their own id's (and possibly style in the future). I do think if we were to go back it could be an interesting separation to consistently put the properties which are about the pointer generally rather than its current location in a separate structure, e.g. pointerType, pointerId. You could also argue that coalesced events and predicted events are separate structures, that are just behind functions instead. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/495#issuecomment-2117651902 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 May 2024 13:48:55 UTC