j

I have officially moved to the 1.1 doctype of XHTML

I currently am looking into the feasability of moving to 2.0 once more than a draft is released.

•
•
•
•
•
•
•
•
•
•
•
•
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
j

Or Hallelujah! Whatever.

I just might have to stop making so much fun of AOL. It seems that the new version of thier connectivity software for MacOS X.2 ships powered by Gecko.

This is truly amazing. So this means that now when an AOL surfer happens upon this site, if they are running 10.2, it will render properly. Amazing. What next, fewer advertisments and better internet service?

Check out this for the full story.

•
•
•
•
•
•
•
•
•
•
•
•
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
j

According to Bobby, I am section 508 compliant.

I am not at this time fully WAI compliant, but I am not that far off, I meet priority 1 requirements. I would like to note at this time that some other sites are not 508 compliant, and are just as bad off as I am in the WAI area.

So, why is my markup invalid, when those who wax poetic about valid markup, are in the same accessability boat I am?

related - validate this site :: validate Random Mumble Generator :: validate worldtimzone

•
•
•
•
•
•
•
•
•
•
•
•
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
j

Well I have just learned that there is to be a MEETUP held here in Lexington. At this time I am acting as host for the event, which just means if you want to attend and need directions email me. The event is for anyone who is in the greater Lexington area and either blogs now, or would like more info about it.

•
•
•
•
•
•
•
•
•
•
•
•
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
j

I have just checked my site with the changes allowing MSIE for windoze to parse my site correctly, and apparently now it has decided to display other elements incorrectly. I have yet to determine the culprit, but now at least the nav menu is not floating over the post content.

I am really getting to the end of my rope with this whole business, I am either going to drop support for IE/any windoze, or create a new layout that does not rely on certian CSS 2 elements that IE borks on. The only caveat of course is that the elememts that IE borks on are ones that are groovy and make CSS2 worth using. Oh well, back to the drawing board.

•
•
•
•
•
•
•
•
•
•
•
•
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
j

Really. Whilst perusing the wordage over at Kevin's, I stumbled across this little diddy:

It's also suboptimal because the information in the JavaScript Console and the W3C validator are aimed at developers. Users need information that is directed at their level. Users don't grok "Error: window._content.document has no properties." It's worse than garbage as far as they are concerned. They need something as drop dead simple as: "This page is broken. The guy who wrote it is a moron." This has the added feature of convincing developers to use web standards, since they likely don't want to be identified as monkeys.

Hmmm. Basil and I agree on something.

Sorta

•
•
•
•
•
•
•
•
•
•
•
•
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

This is Sillyness Spelled Wrong Intentionally. Going strong for 9 years, 8 months and 3 weeks