3 ms·
I understand the frustration behind Google abandoning Pointer Events, but they have good reasons for doing so. For years, one of the bars to get a new feature
by bsimpson 12y ago
I understand the frustration behind Google abandoning Pointer Events, but they have good reasons for doing so. For years, one of the bars to get a new feature added to Chrome has been "Does this increase or maintain performance?" For Pointer Events, they determined the answer was "no" because of the extra hit testing it requires, and they refuse to regress performance on the web.
My primary input device has been a stylus for over a decade, so I'd love to see unified input support on the web, but with all the talk of getting to 60 FPS, I can understand why a spec that contradicts that isn't being implemented.
https://code.google.com/p/chromium/issues/detail?id=162757#c64 https://code.google.com/p/chromium/issues/detail?id=162757#c...