Linked by Kroc Camen on Sat 26th Jun 2010 10:48 UTC
Internet Explorer Microsoft have released IE9 Platform Preview 3, an application that gives developers access to the IE9 rendering engine (it's not a full browser). In this update they have added hardware accelerated HTML5 Video, Canvas, Fonts (using WOFF) and big improvements in JavaScript with ES5, DOM Traversal, L2 and L3 events and 83/100 Acid3 score. It sits between Firefox and Chrome 6 on JavaScript speed, but outperforms every browser in real tests.
Thread beginning with comment 431743
To read all comments associated with this story, please click here.
Hmm ...
by kristoph on Sun 27th Jun 2010 23:16 UTC
kristoph
Member since:
2006-01-01

The amount of work presented here (and the manner in which it is presented) shows a firm commitment by Microsoft to participate in the web in a way that makes developer’s lives easier and allows for all new innovations in the native web. (H.264 aside, mind). As mentioned before, this is in stark contrast to Apple, and the Microsoft of the IE6 years.

Could you explain why you say this?

AFAIK Safari 5 (and WebKit in general) is the most ACID conformant browser. Which, is why - one would imagine - WebKit has been adopted by Google, RIM, and Nokia.

]{

Reply Score: 2

RE: Hmm ...
by smitty on Mon 28th Jun 2010 01:56 in reply to "Hmm ..."
smitty Member since:
2005-10-13

AFAIK Safari 5 (and WebKit in general) is the most ACID conformant browser. Which, is why - one would imagine - WebKit has been adopted by Google, RIM, and Nokia.


I don't think they care much at all about being ACID compliant. They chose WebKit because it's fast, and therefore well suited to be run on phones and other low power devices, and because the codebase is by far the cleanest, easiest to understand, and easiest to integrate into their own products of the main browser engines.

Reply Parent Score: 2

RE: Hmm ...
by Neolander on Mon 28th Jun 2010 08:01 in reply to "Hmm ..."
Neolander Member since:
2010-03-08

The amount of work presented here (and the manner in which it is presented) shows a firm commitment by Microsoft to participate in the web in a way that makes developer’s lives easier and allows for all new innovations in the native web. (H.264 aside, mind). As mentioned before, this is in stark contrast to Apple, and the Microsoft of the IE6 years.

Could you explain why you say this?

AFAIK Safari 5 (and WebKit in general) is the most ACID conformant browser. Which, is why - one would imagine - WebKit has been adopted by Google, RIM, and Nokia.

]{

True, but Apple also favors proprietary standards like H.264 and -webkit tags. Just like Microsoft did with IE in the old days : embrace (existing web standards), extend (with proprietary tags and ActiveX, unfair tactics to crush competition), extinguish...

Edited 2010-06-28 08:02 UTC

Reply Parent Score: 1

RE[2]: Hmm ...
by arpan on Mon 28th Jun 2010 10:16 in reply to "RE: Hmm ..."
arpan Member since:
2006-07-30

A browser prefix is the correct way to introduce new proposed features into CSS.

The browser prefix is a way to test the implementation practically, to see if it fulfills the need it was created for. For example, Webkit & Firefox (Gecko) implement background gradients with different syntax. I think it was first proposed and implemented by the webkit team, but the Firefox team decided that they preferred to implement it in a slightly different and simpler way.

After this is done and they get feedback, they discuss and decide which is the best implementation, and once it it finalized the prefix is removed.

Which is what was done in the latest webkit version, where the -wekit- prefix is no longer necessary to use border radius.

The prefix is used so that it is clear that this is not the final version, and to use with care.

BTW, just so you know, all the rendering engines have a prefix not just webkit.

Webkit: -webkit-
Gecko: -moz-
Opera: -o-

Reply Parent Score: 2