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 13th, 2006 at 10:45 pm
Wow, this is like one of the nerdiest post ever! :p I doubt my blog is even 1.0xhtml validated, nor do I care. Wordpress’s toolbar thingy doesn’t show up on the macs (or at least safari, haven’t checked firefox) so I type out the html code as I write out post and often carelessly… =.=; As long as it’s not SO bad that i’m breaking xml and the rss feeds, I’m happy.. XD
December 13th, 2006 at 10:52 pm
is this anime blog or some web design blog. pfft
December 13th, 2006 at 11:20 pm
oh noes! this page doesnt validate!!
December 13th, 2006 at 11:25 pm
Funny, when I follow the links to check this page, the two tests fail.
The CSS gives a awful lot of warnings plus one error, and the XHTML test fails too. I took a look at the source, and I think it’s because the ‘div’ tags for the comments with a even number have an empty class attribute, whereas the ones with an odd number have the class “alt”.
But I guess you didn’t have any errors while you were testing, because there was no comments at that time.
December 13th, 2006 at 11:33 pm
I got 84 xhtml errors… 91 at first, and gave up after fixing a few. I just hope my blog isn’t broken for any people out there.
I DO salute your presistance though, I really can’t stomach fixing them all…. ^_^
December 13th, 2006 at 11:33 pm
Ops. Should’ve tested the comments. That said, CSS warnings are normal. It doesn’t invalidate the stylesheet.
December 14th, 2006 at 12:55 am
P.S. The geeks shall inherit the Earth. :P
December 14th, 2006 at 12:55 am
Not to be a bitch or anything but if you’re going to claim “xhtml validity” you should be sending pages as mime type “application/xhtml+xm”, Not “text/html”.
December 14th, 2006 at 12:59 am
Oh well, it might be wasted effort if someone posts a comment that doesn’t comply with the standards. Let me try.
December 14th, 2006 at 3:34 am
Nice.
BTW, you should consider writing a small script to fix the archives to XHTML 1.1. It should be an interesting challenge.
December 14th, 2006 at 9:45 am
Hahaha…. dropped to xhtml 1.0 strict XD
still better than the rest though :/
December 14th, 2006 at 4:41 pm
Yeah the sucky thing about changing mime-type to application/xhtml+xm is that there’s no room error. One mistake and the xml-compliant browser will throw an orange screen of death. :(
I’m too lazy to write a SQL query to fix all the old entries. orz
December 14th, 2006 at 5:27 pm
This is why putting display markup in actual entries is bad. You should have some kind of intermediate markup which can be translated into $STANDARD at runtime. ‘bbcode’ or whatnot.
Go and fix them :P
Also, your doctype declaration is now wrong. Firefox whines about it, and I see a ‘]>’ at the top of the page.
December 14th, 2006 at 5:43 pm
I was playing around with internal subsets but it seems that Firefox will only accept them if I change the mime-type.
Everything back to nomal. Sort of.
December 14th, 2006 at 6:08 pm
i think technically you can server xhtml1.1 using text/html, and still call it xhtml1.1 conformant…
if you look here:
http://www.w3.org/TR/xhtml-media-types/#summary
it says for xhtml1.1 you “SHOULD NOT” use text/html.
these SHOULD/MUST/MAY things are defined in rfc 2119:
http://www.rfc-editor.org/rfc/rfc2119.txt
where it says:
SHOULD NOT This phrase, or the phrase “NOT RECOMMENDED” mean that
there may exist valid reasons in particular circumstances when the
particular behavior is acceptable or even useful, but the full
implications should be understood and the case carefully weighed
before implementing any behavior described with this label.
which, imho means you can use text/html.
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.