As the MIX 07 show approaches (I’ll be there Sunday/Monday, then giving a talk at UC Berkeley on Tuesday), I’ve been focusing on what might seem like trailing-edge issues. Last night, for example, I was up way too late rewriting my cross-browser LibraryLookup script — partly to fix a bug, but partly to improve my understanding of how the two supporting technologies, Greasemonkey and Turnabout, could work together to deliver powerful capabilities to millions of people who have yet to experience those capabilities. (See below for some specific notes on Turnabout.)

Also, since I have a couple of talks upcoming, and since I prefer to make and use web-style presentations rather than PowerPoint presentations, I’ve been revisiting HTML Slidy. Here too, I’m paying close attention to cross-browser compatibility issues. After updating to the latest version of Slidy, I’m getting decent results on IE7, Firefox, and Safari.

Although the star of MIX 07 will be Silverlight, it’s important to note — as I mentioned the other day — that Silverlight is a browser-agnostic citizen of the web. Which raises the question: How is Internet Explorer’s own web citizenship coming along? There will be four MIX sessions on IE. One’s by Chris Wilson, who co-chairs the W3C HTML Working Group and whom I interviewed here. Another is by Molly Holzschlag, who is a leading web standards expert and advocate now partnering with Microsoft to advance standards and interoperability, and whom I hope to interview for a future Channel 9 podcast.

Now, more than ever, this work is critically important. It’s true that a more interoperable web is a rising tide that lifts all boats. But we’re also about to break some new ground with Microsoft Silverlight and Adobe Apollo, technologies that build on existing web standards but will also (in my opinion) lead to new ones. As the competition to create those new standards heats up, it will be crucial to ground it in cooperative agreements about the foundation they’re built on.


Notes on Turnabout:

  1. Installing scripts.
    It should be possible to right-click the link to a script, like this one, and install it that way. But that’s not working for me, and the alternative — downloading the script and installing from Turnabout’s options dialog — will be offputting for most folks.
  2. Uninstalling scripts.
    As a script developer, I’ve noticed that uninstalled scripts don’t seem to go away. In order to reliably test new versions I’ve had to completely uninstall/reinstall Turnabout.