I assume it’s just coincidence, but some days it just doesn’t pay to have Mozilla bugs filed about your site:
WindowsITPro also came up in passing in bug 290455, which is asking for the “Live Bookmark feed failed to load” to be clickable through to a more detailed error page. I’m not sure that’s really the way to go, but it’s going to take either Vlad getting done with storage and coming back to us, or someone else picking up Live Bookmarks to do some separation of errors first. Bug 278247 is already laying claim to clicking on “failed to load” to reload the feed: we really need to split “failed to load (because you were offline, or your connection was hosed)” off from “failed to load (because it can’t be parsed, or lacks the title|date and link we require)” to do anything. Even then, I’d think it would be better to try packing the error message into a tooltip (“Not found. Click to reload.” or “Parsing error. Click to validate“), hard though it would be to explain “That might be a valid feed which simply lacks either titles or dates on the items, or maybe it doesn’t have any items, or maybe it’s got some structural error, RSS 2.0 with items outside the channel, or RSS 1.0 with URLs that don’t match between the items rdf:Seq and the rdf:about on each item” in a tooltip.
Oh, WindowsITPro? They were the example of not parsing, with an RSS feed with all the element names in all uppercase. Err, hello? XML is case sensitive: if you’d like to publish an article about that, for your “IT Pro” audience, I could probably write you one.
I’m amazed that there are enough super-ultra-liberal-XML-“parser” using RSS readers out there to let them get away with that: as RSS Bandit said to me when I tried to add it, “that doesn’t look like RSS.” Bloglines? You’re not helping us, swallowing that and pretending it’s RSS.