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.
Thread beginning with comment 552455
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Can't think of anything obvious. Most of these sites are done by designers that abuse -webkit prefixes.

I usually never return to them and I am certainly not going to keep a list.

A lot of the sencha touch toolkit only worked in Chrome/Safari as of last year ... is the only example that sticks in my mind ... which I thought was pretty poor.

I am sure you might call bullshit, but considering the -webkit prefix abuse has been called out on quite well respected blogs such as quirksmode ... There is plenty of evidence the problem exists.

Edited 2013-02-14 16:15 UTC

Reply Parent Score: 3

Nelson Member since:

Any website using touch / animation usually uses WebKit extensions.

But its must more than that, there's a shitload of WebKit only extensions that are used by plenty of "iPhone Optimized" websites around the internet.

You need look no farther than Apple's own developer documentation to see how bad things are. Also, anyone who does this kinda thing for a living can attest to the absolute clusterfuck that this is.

Reply Parent Score: 3

lucas_maximus Member since:

I do this for a living, I mainly still work on the now not so cool "desktop website" for a major gaming company in UK. Though my title is front end I spent most of my time re-factoring and adding new features to a large C# codebase. For the most part I enjoy my job.

We are adding in some touch functionality, but we have bigger problems at the moment which are more to do with version control and fragmentation.

I am constantly frustrated though that people think that because something is open source that there immediately isn't a problem.

For those that are using a browser it is fine and I enjoy using the newest Firefox. For those developing it is a different story and tbh I think in a worse state (mainly due to it being transitional).

Reply Parent Score: 2

cdude 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