The navigation links macros did not yet create title attributes. Mark Pilgrims explanation clearify that the title is very useful, so I changed the macros. The macros can also create normal hyperlinks, which will also get the rel="prev" or rel="next" attributes. I wonder if there's software that does something with rel attributes on <a> elements. Mozilla shows it in the properties window of the hyperlink, but I think that's all.

Mark Pilgrim is doing a brilliant series entitled "30 days to a more accessible weblog". Today he talkes about adding <link> elements to your weblog. I have had these links in my weblog for a while now and made the Radio Userland macros available for download.

Radio's Aggregator supports RSS Auto-Discovery. It's a nice start, but it doesn't work on my site. Why? Because Radio tries to parse the page as xml, and if it fails, it looks for a link element. But this page is valid XML, so that doesn't work. But I'm sure Dave is already working on that.

Thanks to Surfmind's Googling Mozilla I found out that my weblog is #1 in Google for "mozilla weblog" at the moment. Maybe a good moment to write about a nice Mozilla CSS option. The height and width CSS properties are implemented differently by Internet Explorer and Mozilla. Zeldman explained this once very clearly. He also gave a solution, but the Mozilla developers have been busy in the mean time. Simply add the property -moz-box-sizing: border-box;, and the width and height of the element will be the same as in Internet Explorer.

When this mania launched, Matt Griffith said: "Now I just need an aggregator that supports it." This comment loomed over my ego. That has to be Radio, I thought to myself. So I got busy and figured out how to do it. I'm going to release the two new parts when I am confident that nothing breaks. [Scripting News]

Ah, I already wondered why suddenly adding a <link> tag became a hot item. w3future has it since about October 2001, when it was discussed on the syndication list. Not that I'm complaining of course. This will hide the RSS technology for the user, who can simply subscribe on the html page.

With Cedant I thought I had found the perfect web hosting. Never had any serious problems, and the problems I had were usually solved within 10 minutes after sending an e-mail, 24 hours a day. But this time they blew it. Flawless web hosting seems impossible.

Cedant upgraded their servers, and it went horribly wrong. Friday I received an e-mail from Cedant, telling me that they were going to upgrade, and asking me to use the new settings starting Thursday. That's right, I received the notification one day after the switch. The switch left my site in complete disorder. 2 weeks old data. PHP settings changed, so most of my examples aren't working. And the CSS is PHP generated, so my site looked like crap. The website root directory changed, so the FTP uploads from Radio Userland failed.

And of course the site of Cedant remains quiet about the problems. Only after I had sent a complaint, I received a small apology:

We apologize for the abrubtness of these changes. There are many factors that have caused this and we regret that this has impacted our clients this way. This was certainly not our intention when these plans were made.