Hi all respondees
Ben Said
...it depends if you're talking about page layout or actual
content - ie. is your business name, logo etc being used in a header;
or are you creating a page which lists a bunch of businesses? For the
former I'd simply use a DIV, for the latter a list (maybe a definition
list).
I am doing the latter.. (a page (or more) of business listings) so I was
wanted an easy way to tie all the relevent information into one nice little
block.
As Lucien said the W3schools states that "The fieldset element draws a box
around its containing elements." with no mention of form controls and
that's why I asked the question in the first place. It was a response to an
"is there a better way to do this" sort of a moment! Also as Lucien said.. i
didnt just want to draw a box visually around a bit of content.. i wanted to
be able to clearly "group" the related information together neatly.
I considered a DL but found it too restricting and I really didn't want a
whole load of div classes with headers & p tages etc churned out repeatedly
down the page. It seemed to me that if the W3 schools definition of a
fieldset was correct and valid then it was ideal for my requirements. The
fact the validator passed it also seemed to me to say that it could be used
in this way. If <fieldset> can't be used this way why does it pass
validation?
So... what to do? I dunno frankly... the jury is still out.
I will say this though ...i think its a shame that when someone takes the
time to respond to a question and states their point of view only to get
shot down in flames and virtually abused. This list is here to enable us to
discuss the implementation of webstandards amongst like minded people and
I'm sure no one is really "hell-bent on abusing the standards".
Cheers
Jackie
----- Original Message -----
From: "Ben Buchanan" <[EMAIL PROTECTED]>
To: <wsg@webstandardsgroup.org>
Sent: Tuesday, June 05, 2007 12:36 PM
Subject: Re: [WSG] Re: Use of Fieldsets other than in form?
Can fieldsets only to be used in forms or can they be used to group any
sort
of related information together (ie: business name, short description,
logo
and link).
The spec's wording is a little vague but by my reading of it, fieldset
and legend are only intended for form controls. Beyond the spec, I
would imagine that the average user's expectation is that
fieldset+legend = form inputs, so purely from a usability point of
view I'd keep fieldsets for forms.
For general content, the heading structure should "group" information
together; and don't forget that although we use them constantly, DIVs
do actually add structure
(http://www.w3.org/TR/html401/struct/global.html#edef-DIV). When I
really want to break up a page into chunks I also use HRs, although
many people contest that usage I think it's valid.
Lists also group related items together; although I do think it's an
oversight of the spec that you can't explicitly associate a label or
caption with lists. Still, a subheading + list is usually a pretty
clear association.
In some ways it depends if you're talking about page layout or actual
content - ie. is your business name, logo etc being used in a header;
or are you creating a page which lists a bunch of businesses? For the
former I'd simply use a DIV, for the latter a list (maybe a definition
list).
Just my opinion, no doubt there will be plenty of others :)
cheers,
Ben
--
--- <http://weblog.200ok.com.au/>
--- The future has arrived; it's just not
--- evenly distributed. - William Gibson
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
__________ NOD32 2308 (20070604) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
