[dev] How to ensure XHTML compliance
Jan Schneider
jan at horde.org
Fri Dec 2 06:54:43 PST 2005
Zitat von "Kevin M. Myer" <kevin_myer at iu13.org>:
> Is there any automated testing in place to validate the HTML that Horde
> generates? I've been meaning to ask that for some time, but haven't
No. I usually use the WebDeveloper Firefox extension from time to time
on random pages.
> didn't display properly. When I did take the time last weekend to do
> it, it was made a lot simpler because I've been using the HTML
> Validator extension for Firefox
> (http://users.skynet.be/mgueury/mozilla/), which is based on Tidy. For
Nice. Didn't know that one yet.
> every page that loads, it parses the HTML and displays a summary of
> Errors and Warnings and it was pretty easy to see that with a missing
> DOCTYPE, the entire header was missing as well. Most pages generate
> warnings and I'm wondering to what degree of XHTML compliance Horde
> strives for. Are pedantic things like:
>
> <a> attribute "id" has invalid value "1"
> The attribute ID is of type ID. As described above, it should begin
> with a letter
>
> of concern?
Yes. Where possible we try to be pedantic.
> Just wondering if its worth my time to investigate the warnings, or if
> things are compliant enough as is... If just a few people used Horde
> with that extension for a little while, a lot of minor non-compliant
> HTML might be caught, but at the same time, you could go crazy with
> some of the pedantic compliant issues as well.
Sounds like a good plan to me.
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
More information about the dev
mailing list