Re: [pointerevents] Clarify coalesce events and predicted event's target (#280)

While it can sometimes be reasonable to mark certain bits "implementation-defined", I still think it would be useful to have a more coherent description of how the various pieces fit together. The current description might lead someone to think that if they were to create a synthetic event these fields would be non-empty, for instance.

GitHub Notification of comment by annevk
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 12 June 2019 07:12:42 UTC