On Tuesday 05 June 2007 13:49:45 Nick Gleitzman wrote: > Similarly, why use a <fieldset> when a simple <div> will do?
I agree with you about what the spec says, but I don't think I agree the spec in this area is particularly good. The reason I have is that I may (and often do) want an interface that looks the same for both viewing and editing a resource, just with the static text replaced by input elements. Using <fieldset> for the form, as is semantically correct, and duplicating the look with a <div> on non-forms seems to be innefficient. Similarly <label> elements can be validly used anywhere (according to the validator service) but the spec explicitly says: "The LABEL element may be used to attach information to controls." I then use <label> in my form, but have to use a <span> (or whatever), styled the same, to get the same visual when displaying the resource in it's non-editable state. This is a bit different be a <label> indicates behaviour for passing focus, as well as presentation. Luke. > N > ___________________________ > omnivision. websight. > http://www.omnivision.com.au/ > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
