codedread

Here are a few links to keep you busy:

• There appears to be a formal agreement established between Microsoft and Novell to develop and support the Linux-based version of Microsoft’s Silverlight, called Moonlight.
• Speaking of Microsoft, Alex Russell of Dojo speaks of how poorly the Microsoft IE team has communicated future plans. I agree. It’s not a way to build trust among web developers who you’ve pissed off for so long. Where’s the news on the next version of IE after 7?
• Speaking of web browsers, Apple announced the iPodTouch, which will soon put WiFi web browsing capabilities (via Safari) into the hands of many a music geek. Couple that with the iPhone now selling for $200 less and I believe that Safari is soon going to be one of the most widely used browsers out there in the Mobile Web, competing head-to-head with the Opera Mini. When Safari 3 gets out of Beta and is distributed to its millions of users, we’ll suddenly see a huge increase in the number of users that can view SVG.
• Speaking of Opera, I mentioned yesterday that Opera 9.5 Alpha 1 was out. Here are some interesting performance results, though Mozilla evangelist Asa Dotzler is quick to point out that Opera still lacks an auto-update feature.

That’s it for now.

I’m pretty happy with the performance of the Opera 9.5 Alpha 1 preview (Codename “Kestrel” - download here). So happy that I decided to finally try and figure out how to make a screencast today. Click To Read More...

The Opera Desktop Team tells us that we should be expecting early builds for Opera 9.5 in a couple more weeks and I’m really looking forward to some of the features: Click To Read More...

At home we’ve all been pretty sick the last week or so. As a result, I only recently caught this nugget. Molly Holzschlag suggests that all work should stop on HTML5, XHTML 1.1+ (and presumably CSS3?). Instead she wants everyone to “COMPLETE HTML 4.1 [sic], XHTML 1.0 and CSS 2.1 in specs and browsers where applicable”, then “WAIT for future HTML, XHTML and CSS implementations until these implementations are complete”. I can forgive the typo of HTML 4.1, but what left me reeling was that someone like Molly doesn’t understand the reasons her suggestions are so impossible. Click To Read More...

Found this article on Wikipedia today that shows the release dates of some of the major web browsers out there. I did my bit to reorganize the table a lil, but more work needs to be done for some of the perhaps less known browsers.

But what I found most cool was this picture, which shows a timeline for all web browsers. If you can’t see the picture, you must not be using a cool browser like Opera, Firefox or Safari. I won’t ask you “why not”… But you can still see the picture at this link, just not as clearly. More web geek discussion ahead … Click To Read More...

I published my results of running ten different SVG implementations through the SVG Test Suite. Click To Read More...

Sometimes it’s not obvious how a document is being interpreted by a web browser. For instance, you might write some XHTML 1.1, but the browser actually interprets it as HTML 4. You may be expecting the browser to be using Standards Mode (recommended), but it might actually be using Quirks Mode because you missed the DOCTYPE statement. I’ll periodically update this blog entry to keep track of how to do this stuff in a variety of browsers. Click To Read More...