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 552449
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Comment by ssokolow
by moondevil on Thu 14th Feb 2013 15:30 UTC in reply to "RE[6]: Comment by ssokolow"
moondevil
Member since:
2005-07-08

As web-developer I thank WebKit for continues fixing and improving the Web at an incredible speed. This is far better then having to deal with IE6 bugs for years to come cause the vendor decided not to fix.


How do you fix Webkit in specific browser versions?

Because the project manager really would like that all the iPad users have the same experience on his company new web site.

Or for that matter all Android users since version 2.2.

I can give more examples.

Reply Parent Score: 3

RE[8]: Comment by ssokolow
by cdude on Thu 14th Feb 2013 23:44 in reply to "RE[7]: Comment by ssokolow"
cdude Member since:
2008-09-21

You seem to demand Webbrowser stay where they are now and all development halts so your quick and dirty hacks against specific browsers and browser-version keeps to work?

How about using an existing framework that does handle possible differences between browser-engines and browser-versions for you? One of those browser-vendors test against and that receives updates if needed.

Its a very bad habit to hack in different code-paths for each browser, each browser-version in your HTML/JS. If you choosed do to that then you shouldn't complain it may and will break.

The alternate, those you seen to demand, is that we alll stick with IE6 and NS4 forever.

How do you fix Webkit in specific browser versions?


I check out the sourcecode, write a patch, create a bugreport, attach the patch, ask for review and commit.

Next iterations of all WebKit based browsers contain the patch. Profit.

Try that with IE. You can't? Aha!

What you demand is a time-machine, stopped development and innovation to keep your hacks working. Maybe the problem is on your side?

Edited 2013-02-14 23:50 UTC

Reply Parent Score: 3