codedread

Google is going to release a new open-source web browser tomorrow (Sept 2nd, 2008) called Google Chrome. Lots of information contained in forty pages of this comic book. The rendering engine is WebKit, but it has its own JavaScript engine (V8) that compiles the JS into bytemachine code and uses more efficient garbage collection. It also follows the thoughts of the Internet Explorer team of putting the tab at the root of the UI and letting each tab be its own process (not just thread). Oh, it comes with Google Gears pre-installed too.

This all sounds good: security, stability, anti-phishing, sandboxing, ’superfast’ JS. Of course there’s only one true test though.

At first I was wondering if this was a fork of WebKit, but I think the only thing that would make sense would be for Google to work in parallel with WebKit (continually updating Chrome’s rendering engine with new versions of WebKit). Everything else would be part of the Chrome open source project. If you’re in the know, drop a line below.

Ok, I’m happy. A completely open source browser that supports SVG and is (sort of) co-sponsored by two big companies with lots of cash (Google and Apple).

I’ve made enough updates over the past week or so on my SVG Web Stats thing to call it 2.0. Here are a list of changes: Click To Read More...

Very cool stuff from roc. An interesting alternative to all the CSS properties being added to WebKit. Meanwhile, Microsoft is still plodding away on bog-standard CSS 2 - expect an update from them in August, if you’re still interested (if you are maybe you want to try a new plugin for IE?)

The last two years have been explosive for WebKit development - the project has really accelerated, moving at a much faster perceivable rate than the other notable open-source web platform, Mozilla. I’ve been noticing more and more innovations that affect web developers from the Safari blog. Click To Read More...

The latest WebKit nightly now has a decent amount of SVG+SMIL (animation) coverage. By my old school grading system, that gives WebKit a solid ‘B’ grade in terms of SVG support (75%). This is what I was talking about a few weeks ago and I’m quite happy to see it happen! If they cleaned up their regressions from a few weeks ago (some problems with SVG patterns, I believe), they might even crest 80%.

After the announcement that the Apple developers have turned on their SMIL support in order to pass Acid3 test, I was excited enough to download the MacOS nightly and run through the SVG animation test suite. I was pretty disappointed. Click To Read More...

WebKit and Opera are really scrambling to be the first browser to fully pass Acid 3. First, Opera claimed they were at 100/100 in a private build, then Ian corrected the test (based on feedback from Apple developers), presumably knocking Opera back to 99/100. And just now, the WebKit guys have turned on SVG Animation (SMIL) in their nightly builds, putting them also at 99/100. This was a surprise to me, since I had heard that their SMIL implementation was not ready for prime-time, so to speak. Oh well, this is great - now we have a second browser implementing SMIL natively and we can truly start pushing for interoperable solutions.

What does it mean for Apple and Opera fans? Probably a lot. What does it mean for web standardistas? Apple and Opera care (more?). What does this all actually mean for web developers at the moment? Not a single thing. Oh well, time to tally up my own similarly-meaningless SVG support score…

[Update 10:25 PM CST: Apple did it. They are the first to achieve 100/100 in Acid3 with a publicly downloadable browser (even if it is only for MacOS)]