Despite bringing my Windows laptop. Despite setting my display to 1024x768. Despite arriving early. Despite testing my laptop with the presentation equipment. Despite all of that, I still couldn’t present from my laptop when my time came. Brad was kind enough to swap time slots to allow me an opportunity to regroup, and further nice enough to let me use his laptop when I still could not present from my laptop despite a total and cold reboot.
That just sucks.
At the present time, this presentation is only known to work on Firefox 3.5. It likely will work the same on Firefox 3.0. I haven’t looked into WebKit and Opera yet, at a minimum, there will be some style differences (e.g. no rounded corners). Over the next few days, I will look into getting this to work to some extent with IE, but given the topic of the presentation, I may not be able to get to 100% there.
The talk did generate a good conversation, both during and after the presentation. In particular, I am confident that Alex will find a way to address my core concerns with Google Chrome Frame, at which time I expect to support it on my blog and planet. One thing that I said to him that deserves wider mention: in general there are two types of technology to me, ones that I criticize (example: XML and HTTP), and ones that I ignore. Google Chrome Frame (or “Chromie” as I prefer to call it) is definitely one of the former.
Just a couple of typos: the head/title element lacks an ‘H’ in “Beyond XTML”; also, isn’t it “degradation” instead of "degredation"? Firefox 3.0.14 on Ubuntu Linux 9.04 seems to behave reasonably. However, the bottom right corner is not rounded; don’t know if that’s on purpose or it’s just a problem of the browser.
Heh heh heh the Firefox SVG-in-img problem. Almost as frustrating as the Firefox SVG-in-CSS problem. Get those fixed and I suspect that SVG adoption on the web would rise significantly, after all Firefox does account for a significant minority of web browser usage.