Chrome drops Microsoft's “Pointer Events” touch input spec in favor of Apple's “Touch Events”
Google to drop Microsoft-designed touch Web spec, stick with Apple tech — Developers on the Blink browser engine, the core component that powers both Google's Chrome browser …
Context & Ripple Effects
This is the third time Google has used Chrome's weight to settle a standards fight by unilateral removal rather than committee consensus. In 2009 it waved goodbye to Gears in favor of HTML5, and in 2011 it floated baking Android-style Web Intents into Chrome; both moves treated the dominant browser as the place where competing specs get sorted out.
Pointer Events was Microsoft's attempt to unify mouse, pen, and touch input behind one interface it introduced with Internet Explorer. With Blink — the engine behind both Chrome and Opera — pulling support and reaffirming Apple's Touch Events instead, the two largest mobile-relevant engines stay aligned on the Apple-originated spec while Microsoft's unification bid loses its path to ubiquity.
First-order effects
- Web developers building touch interfaces can now target Apple's Touch Events across WebKit and Blink without hedging, while any code written against Microsoft's Pointer Events loses Chrome support outright.
- Microsoft's Pointer Events standard is left running only in Internet Explorer, turning a cross-input unification spec into a single-browser feature.
Second-order effects
- Site authors who want unified pointer handling face a fork: dual code paths per engine, or abandoning Pointer Events — which pushes Microsoft toward implementing Touch Events in IE just to keep its own spec relevant.
- Opera, as a Blink shipper, inherits the decision automatically, shrinking the pool of engines where Microsoft's spec ships without Microsoft negotiating anything.
Third-order effects
- If the pattern holds, 'web standard' increasingly means whatever Blink implements, and standards bodies become ratifiers of decisions already made by the dominant engine — a structural shift in where control of the web platform actually sits.
- Microsoft's strategy of seeding cross-platform specs through Internet Explorer loses leverage whenever Chrome declines to follow, encouraging vendors to design specs around the engines they control first and standardize later.
The trend: Chrome's market share is turning it into the de facto arbiter of which competing web specifications survive, with other vendors' standards living or dying at Google's discretion.