- From: Daniel Libby via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Sep 2019 21:57:39 +0000
- To: public-pointer-events@w3.org
Yes, it is true that even with pointerrawupdate and prediction, there is still a gap in latency. I like the simplicity of specifying a cursor-like image for the UA to draw trailing the pointer, but in practice it will lead to undesirable artifacts, mainly because the stroke that is drawn by the app would not be taken into account. Inking applications on the web already follow the pattern of ‘consume pointer event, produce strokes on a canvas’. This can be enhanced by things like pointerrawupdate, prediction, input delivered to workers, etc. without requiring web developers to change their underlying programming or data model. Similarly, I’d like to propose an additional enhancement to expose OS capabilities for drawing a 'cursor trail'. Conceptually, we need to communicate the following information to the OS to enable this: • Which pointer events were consumed and rendered as ink strokes • Metadata around the ‘style’ of the drawn stroke, e.g. color, radius, tilt, pressure Current thinking is that the metadata is limited in scope and is not designed to accommodate arbitrary shaders or complex images. Another option could be to expose supported metadata properties via a capabilities query. We’re still working on the ergonomics and doing some prototyping, but I would love to get this groups feedback on whether a proposal along these lines make sense. -- GitHub Notification of comment by dlibby- Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/204#issuecomment-527656843 using your GitHub account
Received on Tuesday, 3 September 2019 21:57:40 UTC