4 ms·
Finally! 'Pointer events' originated at Microsoft, after the W3C effort to standardize Apple's 'Touch events' became uncertain due to patent issues. For a whil
by niftich 10y ago
Finally!
'Pointer events' originated at Microsoft, after the W3C effort to standardize Apple's 'Touch events' became uncertain due to patent issues. For a while, despite admitting it's a more elegant spec for unified input, Google were reluctant to add it because Apple wasn't interested [1][2].
Now Google have changed their mind once more and shipped this, making Apple the only major outlier. The pains of shimming these similar-but-different APIs will continue for a bit, but hopefully Apple will make this concession in the end.
[1] https://timkadlec.com/2015/02/apples-web/ https://timkadlec.com/2015/02/apples-web/
[2] https://mobiforge.com/news-comment/who-wants-pointer-events-api-everyone-nearly https://mobiforge.com/news-comment/who-wants-pointer-events-...
- Klathmon 10y ago>making Apple the only major outlier That does seem to be a theme with web technologies and Apple recently. I hope their recent work on Safari 10's compatibility continues.
- pkulak 10y agoHow difficult would a TE -> PE library be to build?
- bsimpson 10y agoYou mean like this one? https://github.com/jquery/PEP/ https://github.com/jquery/PEP/ Was built by the Polymer team before Chrome deprioritized Pointer Events the first time round, and transferred to the JQuery Foundation thereafter.
- pkulak 10y agoGood to know. Thanks!
- riskable 10y agoThis one has you covered ;) https://github.com/liftoff/HumanInput https://github.com/liftoff/HumanInput Wrote it myself.