Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Opera Software De kogel is door de kerk: as we already talked about earlier, Opera is going to switch to the WebKit engine, leaving its own Presto rendering engine behind. We didn't yet know if they would the switch only on mobile or on the desktop as well, and they cleared that up too: both mobile and desktop Opera Browsers will switch to the WebKit rendering engine.
Permalink for comment 552662
To read all comments associated with this story, please click here.
Member since:

-webkit prefixes

The w3c even suggests the use of browser prefixes for yet not stable and standardized API. Once the API is stable and standard prefixes are removed.


WebKit is the only browser engine supporting the 2 existing touch interfaces including Microsoft's very own one. Both touch interfaces (including Microsoft's) didn't made it through the w3c yet too. Good example from yours validating the need for the prefix case :-)

shitload of WebKit only extensions that are used by plenty of "iPhone Optimized" websites around the internet.

Most of them supported by e.g. Firefox. HTML5 is a living standard and it takes some time till de facto standards made it through the w3c committees, into the specs and till a new version of the specs is published (how many years took HTML5? right). Meanwhile browser-vendors like Firefox, Opera, Google, Apple, Blackberry, etc work well together to define what comes next, implement it (with prefixes), get it stable, push through w3c, remove prefixes.

See such prefixes as "future" namespace with private API that is subject to changes till it becomes official public API.

Exactly this concept is the reason why HTML development accelerated so much within last years compared to the many many years before.

Edited 2013-02-15 19:08 UTC

Reply Parent Score: 1