]> Something Witty Goes Here

codedread

Archive for the ‘Firefox’ Category

New XHTML+SVG Theme

Monday, February 18th, 2008

I’ve been tinkering at a new theme for my website since the Christmas holidays and finally got around to flipping the switch this weekend. I decided to try my hand, for the first time, at real XHTML served as application/xhtml+xml but with PHP content negotiation to text/html for poor ol’ Internet Explorer. Click To Read More...

FXPointer - Link Exactly

Tuesday, October 30th, 2007

How many times have you told a friend or colleague “Go to http://example.com/some/doc and search for XXXX” ? I do it a lot actually. Ideally web pages should identify significant sections of a web page with identifiers (id=”foo”) so that you can link to http://example.com/some/doc/#foo, but the problem is that not everyone follows this practice. In fact, there are a lot of big specification documents where you’d like to point someone to a specific paragraph to save someone time and encourage them to actually visit the link and read it. This becomes increasingly important as the mobile web accelerates and small screens with harder-to-use keyboards become more prevalent. I hope this Firefox extension will help. Click To Read More...

SVG Support Updated

Wednesday, July 4th, 2007

Happy July 4th, for those who have it off… Renesis 0.7 was released today and so was Firefox 3 Alpha 6 - so I spent an hour or so wading through the SVG Test Suite to update my SVG Support page. Good news: Renesis 0.7 has made great strides in the last two months. Bad News: Despite Firefox 3 Alpha 6 having some new functionality (a couple filters were added), there were some regressions. If I can find the time, I’ll investigate and open some bugs.

Another thing: I can’t get Renesis to work on any of my embedded SVG files or SVG served via PHP. Something I’ll have to bring up with the Emiasys guys…

Molly’s Grenade

Friday, June 22nd, 2007

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...

codedread codedread