I’ve spent some spare minutes here and there over the last several days working on a new theme for the site. Try out my Halloween Theme.
Theme switching requires Javascript and at least a moderately modern browser. Even Netscape 4 users can get some of the effects (though it messes up the menus on the left for some reason).
One of these days I’m going to clean up my HTML and do some more interesting theme variations….
Spooky!Related posts:
- Web Design-o-rama
" Netscape has redesigned their DevEdge site with loads of standards-compliant goodness. Their hybrid CSS/DHTML menus are exactly what I’ve been looking for! Wow, not..." - Choosing Standards
" There’s an old saying in the computing field: “The great thing about standards is that there are so many to choose from.” Funny, but..." - AOL Axes Netscape
" The big news in the web development community right now is that Netscape is dead. AOL is laying off or reassigning employees that were..." - More validation than you can shake a stick at
" I spent a few minutes digging through my HTML and my blogging software source, and this page now validates: It still looks like poo..." - Don’t ever change
" Okay, a few changes here. Removed the javascript that would automatically open links in new windows. Removed BlogSnob ad box. Removed the Blogdex metalinker..."














4 Comments
Your parsed html stinks, mate. If you cleaned it up (see my answer to your mail to css-d), you’d probably get it both to work in more browsers and be much shorter in code.
Vurrently, if I chose the Halloween theme, you put no less than three link tags to the halloween stylesheet in the page, of which one is alternate (default disabled, switchables) and the other two are persistent (always enabled, nonswitchables).
In short, your mistake is that you write additional elements instead of modifying the old ones.
Well, I admit that the HTML has problems (I comment on it right at the top of the source). But yeah, I finally figured out that the real problem is that switcher code I’m using. When I have time to look at it again, I’ll try changing to the switcher code from A List Apart.
Instead of that switcher, I’d recommend you to use my own ThemeSwitcher.
The one Paul Sowden wrote doesn’t supply all ways of defining alternate stylesheets – mine does. It isn’t backwards compatible with 4th gen browsers, though.
Okay, done