This Page Is Valid XHTML 1.1!

I did a little more tweaking and now This Page Is Valid XHTML 1.1!

Again you have to try it with the source from a browser like Firefox, if you just point the validator at this page it renders down level which is not compliant.

I should note that the FCKeditor is only XHTML 1.0 compliant so any page with an editor will not validate against XHTML 1.1 until that support is in place. In any case since browsers seem to be forgiving I think I can still go forward with the XHTML 1.1 DOCTYPE

Also I had to fix even more content in the db where I have historically had the bad habit of using target=_blank on links to external sites. target is no longer valid in XHTML 1.1

This site is also currently using much more CSS layout and most of the table layout has been removed. I'm still working on a few areas of this and still need to update more of the built in skins to work with the new model but I figured it was good to go ahead and do the skin for this site first so I can test it in the real world.

Thanks go out to Alexander Orlov for help and good advice in working toward XHTML compliance.


Jasmin Savard

re: This Page Is Valid XHTML 1.1!

Monday, February 20, 2006 5:33:18 AM

Why was the target attribute removed from XHTML 1.1?

It wasn't. XHTML 1.0 comes in three versions: strict, transitional, and frameset. All three of these were deliberately kept as close as possible to HTML 4.01 as XML would allow. XHTML 1.1 is an updated version of XHTML 1.0 strict, and no version of HTML strict has ever included the target attribute. The other two versions, transitional and frameset, were not updated, because there was nothing to update. If you want to use the target attribute, use XHTML 1.0 transitional.

I took this text from W3C website about XHTML 1.1
so I think you should keep your target attributes and just convert to XHTML transitional.


re: This Page Is Valid XHTML 1.1!

Monday, February 20, 2006 2:24:07 PM
Hi Jasmin,

Since the doctype is set in the Master page, people will be able to use whatever doctype they like. I am going to make the built in skins set at Xhtml 1.0 Transitional but not because of the target attribute. The reason it is better to use 1.0 Transitional for now in mojoPortal is that the FCKeditor is not 1.1 compliant because it uses iframe and I don't think that will change very soon. Some pages of mojoportal could validate as Xhtml 1.1 but if we use that as the doc type it will not be valid on all pages. Using Xhtml 1.0 Transitional it will be posible to make every page including those that use an editor like this one validate.

As for target, people can use that even if the page doesn't  validate, browsers don't mind. Myself I have always used target=_blank when linking to external sites because I don't want people to leave my site but after much thinking about it I understand the reason it goes away in 1.1 and I agree with it. The user should be in control, even though I have linked that way I always found it nuisance when sites do that, if I want to keep my place I right click and open in a new tab, otherwise I want it to go where I click and if it does something different I don't like it. With web newbies opening new windows just frightens and confuses them. These are things best left to user control and browser preferences no matter how much we would like to keep people at our sites. So myself, even though I will be using the Xhtml 1.0 Transitional which allows target, I am no longer using target in my links. But anyone who wishes to continue doing that can do as they wish.

I have set this site back to Xhtml 1.0 Transitional and now even this page validates. I also added a .browser file to detect the w3c validator so now the link at the bottom goes right to the validator which makes it easy to check the pages in this site. Most of them should be valid now.


Comments are closed on this post.