K-Squared Ramblings

Rumbling toward IE8

My feed reader is filling up with commentary on Microsoft’s proposal to lock web pages to specific rendering engines (funny how it doesn’t sound quite so forward thinking when you put it like that). Rather than link to a lot of them, I’ll just link to Opera Watch’s post which collects quotes from various standards & browser people.

The IE7/IE6 ratio on this site is still holding above 1 for the month (yay!) at 33.6% to 28.3%.

Also interesting: last week we got our first visit from Internet Explorer 8. Just one visit to Katie’s analysis of Wolfram & Hart’s work comp liability, but it loaded the relevant images, styles, etc., so it looks like an actual browser visit (and not some bot using a fake UA, like the spambot that keeps trying to post comments as Firefox 9). More importantly, it actually came from an IP address that’s assigned to Microsoft and resolves to a microsoft.com hostname, so I think it’s the real deal.

IE8 will pass Acid2

Okay, this will mean nothing to most people out there, but to web developers, particularly those who use standards-based design to maximize compatibility with different browsers, this is monumental.

An internal build of Internet Explorer 8 has passed Acid2.

The Acid2 test was released in April 2005 to test a number of pieces of the HTML and CSS standards that, at the time, no modern browser handled according to spec. The purpose of the test was to prod browser developers into improving their products, and to do so consistently, so that developers would have more tools available for cross-browser sites.

At the time, Microsoft dismissed its its importance entirely. Even though they were working on rendering improvements for IE7, they stated that Acid2 was not one of their goals. Meanwhile Opera and Firefox were both in the wrong phase of their development cycles to make sweeping changes, so Safari jumped on it and became the first browser to pass. (Every once in a while I see someone say Opera was the first, and I have to wonder where they were.) Opera followed with version 9, and the Firefox 3 betas pass it as well.

With Gecko (Firefox), WebKit (Safari), Opera and IE accounting for the four biggest web browsers and the most popular minor browsers (Flock, Camino, Shiira, etc., plus IE shells like Maxthon), this shows unprecedented convergence among clients. It will be much easier to develop a cross-browser website that runs on IE8, Firefox 3, Opera 9+ and Safari 3+.

There are, of course, many aspects of the specs that aren’t covered by Acid2. And there are emerging standards like HTML5 and CSS3. And there are plenty of other bugs, quirks, and extensions among various browsers (IE’s bizarre concept of having layout, for instance, trips up all kinds of weird issues). And then there’s waiting for IE8 to be released, and moving people up from IE7, not to mention all the people we still have to move up from IE6. Full benefit is probably at least 3 or 4 years away. *sigh*

(via WaSP Buzz)

Legality Links

Organization for Transformative Works – dedicated to protecting the expression of fan fiction, fan art, etc. (via Naomi Novik)

Open Standards, One Web, and Opera – Just why are standards important, anyway? (via Opera Watch)

Speaking of Opera, their EU antitrust complaint against Microsoft has been making waves. Responses at CSS3.info, Web Standards Project, Slashdot (edit: more Slashdot), Asa Dotzler, Opera Watch, plus a Q&A w/ Haarvard. My take: Good luck on unbundling, but if they can force Microsoft to catch up with the rest of the market in terms of standards support, I’m all for it.

Nissan vs. Nissan. On my way to work I saw a bumper sticker on an XTerra that said “In support of our freedom, it’s my last Nissan.” Huh? There was clearly a web address below it, but it was too small to read at that distance. So I looked up the phrase, and apparently there’s been a long-running dispute over the domain name nissan.com, between a small computer business named after its founder, Uzi Nissan, and the Nissan car company. The dispute was eventually resolved (correctly, IMO, since he has a legit reason to use the name) in favor of the little guy. On the other hand, I don’t see why the site makes such a big deal about Nissan’s “French Connection” to Renault.

Don’t Hurt the Web

The Mozilla Developer Center has just posted some desktop wallpaper promoting open standards, (and the MDC itself) with the theme, “Please don’t hurt the web. Use open standards.”

Apparently the design was a big hit as a poster at SXSW.

For those who haven’t seen it, the MDC is a great developer resource for web developers, describing lots of standards along with Mozilla-specific information.

(via Rhian @ SFX, who notes that the image is available for use under the terms of the Creative Commons Attribution-NonCommercial license. These wallpapers are also covered by the Mozilla Trademark Policy.)

Unlikely Partnership

Here’s a surprise: web standardista extraordinaire Molly Holzschlag is now working with Microsoft to promote web standards within the organization.

Improving interoperability, especially at high-profile services like many of Microsoft’s, is critical to the future of the web. I can only hope that the emphasis on standards will feed into the design goals for Internet Explorer 8—and that IE8 will be released before Windows XP drops from mainstream to extended support in 2009.

Advantages of standards-based design: Compatibility

Microsoft is really pushing for people to make sure their websites and apps are compatible with IE7. Apparently this is a real concern for a lot of people who relied on certain proprietary features, bugs, and quirks in IE6. I guess they figured they wouldn’t have to worry about future versions. (Hmm… I wonder where they got that idea?)

The fact of the matter is, I’m not worried. I tested my personal sites and the sites I’d built for work months ago, using the IE7 betas, and more recently with RC1. I made a couple of minor changes to some stylesheets, but that was about it.

Why? I’ve been writing standards-based code for years. I validate it from time to time, and I test to make sure it works in the latest versions of Firefox, Opera and Safari as well as IE. So the code was already portable.

Plus, anything new I’ve built since January has been designed with IE7 in mind from the beginning.

Most of the changes were to workarounds for IE6. Either stopping them from running on IE7 (if the bug was fixed), or keeping them running on IE7 (if it was done using a CSS hack).

WaSP/Microsoft Collaboration

The Web Standards Project has announced a joint task force with Microsoft to promote web standards in products like Visual Studio and ASP.NET.

I imagine this was probably a factor in the decision to divest themselves of Browse Happy last month. Certainly this project is more in line with their core mission—promoting the use of standards on the web—and fits right in with the Dreamweaver Task Force they ran with Macromedia back in 2001.

(via WaSP Buzz)

Acid2

The Acid2 Browser Test is out, and any fears that it’s focused only on IE have proven unfounded. As Dave Hyatt remarks in his efforts to get it to work in Safari, “Every browser fails it spectacularly.”

The Acid2 test is a single page of HTML and CSS designed to use parts of the spec that today’s browsers handle incorrectly or not at all. According to the rules, the code should display a happy face… but at the moment it produced varying levels of gibberish. So far Firefox seems to handle it the least badly (I hesitate to say “best”), with Opera and Konqueror at about the same level (you can at least see a circular outline), and Internet Explorer looking like a piece of modern art.

Well, we know Safari is working on it (and the fixes should feed back into Konqueror). One of the test’s architects is high up at Opera, so you can bet they will be improving. I imagine people are already submitting bug reports to Mozilla. [Update: found the tracking bug in Bugzilla.] That leaves Internet Explorer. They’ve been notoriously reluctant to update their rendering engine, but they did ask for specific requests. I don’t have much confidence in seeing fixes in IE 7, but you never know…

Anyone want to place bets on who progresses the fastest?