Hi, I'm making a paint app, and I've found getCoalescedEvents incredibly useful, really bringing my app to a professional level art program. I read that this feature is removed from the spec and can be removed from browsers at anytime (this link: https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/getCoalescedEvents)
Is there anything that can be done so that this extremely useful API is not removed but becomes standard??
Thank you
I don't know why that is mentioned in the MDN. But that assessment it not correct. This feature is here to stay for now and there is no plan to remove it from anywhere. Not the spec nor the implementations. I'll follow up with MDN to fix that text. Thanks for the feedback btw. Could you also comment on github issue
https://github.com/w3c/pointerevents/issues/22
as it is always helpful to hear developers feedback and makes it easier to push standards and new features.
btw since you are making a paint app you might be interested in another powerful feature pointerrawmove
https://github.com/w3c/pointerevents/issues/214
in conjunction with off-screen canvas. This will let you reduce the latency you see in your paint app even further so it feels more like a paper drawing. Again the feedback on github issue is always appreciated.
Hi, that is great to hear.
This pointerrawmove also sounds very interesting.
Is there anything specific you want me to comment on on the github page for getCoalescedEvents ? Is there still an issue with getCoalescedEvents ??
getCoalescedEvents is not still in the main track of the pointerevents specification. So having developers that have some use for such an API make a more compelling case for a new API like this.
Comment 1 by nzolghadr@chromium.org
, Oct 17 2016