XHTML 1.1 Validated (no longer)
EDIT: Ops, I forgot that I can’t change the mime-type to application/xhtml+xm because my older entries will commit seppuku. Oh well, back to 1.0 Strict.
This blog is now XHTML 1.1 XHTML 1.0 Strict and CSS validated. If you don’t know what this means and/or don’t care: nonsensical technobabble after the jump.
I spent some time today modifying the code for this blog to make it XHTML 1.1 and CSS validated. I upgraded it from XHTML 1.0 Transitional to XHTML 1.0 Strict a few days ago, and I noticed that 1.1 is not much different. The only thing that was invalid between 1.0 Strict and 1.1 was Lightbox’s usage of angular brackets in the “rel” attribute, so I modified protoype.js and changed the syntax to look for dashes instead.
inspect: function() {
return '-' + this.map(Object.inspect).join(', ') + '-';
}
Everyone says that 1.0 Transitional is enough and Strict is just overkill. Pffft. Just wait till I get it validated on 2.0. (As soon as the working draft is finalized.)
That said, although the layout is validated, a lot of the older entries aren’t. I guess there’s no point fixing them since none of you read the archives anyway. :P Those &, lightbox[], <strike> and <u> will just have to stay where they are for now.
That said, I’m pretty sure DM.com is now the only XHTML 1.1 1.0 Strict validated anime blog in the world. Hurray! I have no life!
If you have a Wordpress blog, consider validating it. Wordpress is valid 1.0 Transitional out of the box and it shouldn’t take a lot of effort to get it back. Just remember to close your <img /> with a slash, use “alt” and keep the <div> out of the <p>. :3
December 15th, 2006 at 11:36 am
Dark Mirage, whose butt is that on your banner? I must know.
December 15th, 2006 at 12:22 pm
LOL much programming talk.. which goes o’er my head. :P
December 15th, 2006 at 2:49 pm
Beowulf, it will be revealed in my latest entry which will be ready soon. :P
January 25th, 2007 at 12:12 am
Hey,
I got here looking for a lightbox hack for xhtml 1.1 (thnkx!) ;)
As for your own validation, consider using a Class instead of an ID on your because if you use it recurrently it’s supposed to be a class… :)
You can configure a class by using “.nameofclass” in your CSS and calling it as ! That would fix the validation error ;)
Nice “one-of-a-million” design :p But it’s good to hear you care of validation even though you don’t seem to be in the web design business anyway :) good good :)
Keep it up m8,
~Levi F.