Roderick A. Anderson wrote:
On Fri, 29 Oct 2004, Dave Cross wrote:

  
You're discussing different things. You're talking (correctly) about
HTML, but Rod is talking (also correctly) about XHTML.

It's well worth considering changinga all of your pages to valid XHTML
- and it shouldn't be too hard if they are generated from templates :)
    

Thanks all.  I have been trying for xhtml 1.0 compliance in all my coding
but I've sometimes found conflicting evidence.  Standards verses tutorials
verses examples.  I was pretty sure I wanted checked="checked" but I've
seen examples where they used all UPPERCASE for the tags which is a no-no
in xhtml.  But I had to ask.  (If you've done anything where the designer 
used Dreamweaver I'll know what a pain it is to get it standards 
compliant.  :-)

Still, all-in-all the change from radio to checkbox made the original 
question well worth the finger effort.

Once I get checky reinstalled I'll be beating the .*html code up again.


Again thanks,
Rod
  
One last comment on this before it dies. The checked="checked" form is cited here in a W3C doc:
http://www.w3.org/TR/xhtml1/#h-4.5

It is specifically recommended as being compatible with old and new formats. Part of the XHTML spec is the guidelines section that deals with making XHTML render (fairly-well) with older clients. Of course, I should point out that it isn't a rule, just a suggestion. :)
http://www.w3.org/TR/xhtml1/#guidelines

This appendix is informative.

This appendix summarizes design guidelines for authors who wish their XHTML documents to render on existing HTML user agents. Note that this recommendation does not define how HTML conforming user agents should process HTML documents. Nor does it define the meaning of the Internet Media Type text/html. For these definitions, see [HTML4] and [RFC2854] respectively.

Finally, see also: http://www.hixie.ch/advocacy/xhtml

--mark mills
Xodiax Engineering


Reply via email to