Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Permalink for comment 552445
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2008-09-21
Then watch how Webkit being open solves their issues when CSS or JavaScript break across Webkit versions.
You not develop against a certain version and vendor but the standard. If behavior/layout changes in WebKit then that happens cause the previous implementation had bugs that got fixed.
Yes, this is a very different approach then what Microsoft does with IE.
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.
Anyhow, everybody who likes the IE6 approach more can go on, make an own WebKit based browser and not fix. Luckly it seems all major vendors decided against that.
Edited 2013-02-14 15:03 UTC