Re: SPAM-LOW: Re: [WSG] semantics of a simple form
The aspx programmer is open to standards and may be receptive to my advice. how about this: fieldset legendRoom Search/legend div class=checkin labelCheck-in Date:/label select name=... option value=101/option /select .. /div div class=checkout label for=...Check-out Date:/label select name=... ./select div class=button input type=submit name=... value=Search id=... / /div /div /fieldset ...allthough when i look at it this nearly feels like a list to me... -best kevin Reading slow these days. An explicit label has two parts: the label with its for attribute and the id attribute in the control. Your example need to have the id attribut equal to the for attribute of the label added to the select: label for=bbbselect name=xxx id=bbb Or use the implicit form which includes the select in the label and therefore doesn't need the for or id attributes: labelCheck-in Date: select name=... option value=101/option /select /label Most form look like lists, don't they? What makes them different is you are collecting data with which something is done. drew *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] semantics of a simple form
On Thu, Sep 25, 2008 at 4:28 PM, kevin mcmonagle [EMAIL PROTECTED] wrote: im not an expert on this but should there be a fieldset or legend around this? not even sure if it qualifies as a form, although it has a submit button. The reference about forms is: http://www.w3.org/TR/html401/interact/forms.html If you are going to see this as a form you are goping to have to rewrite it to include labels and other requirements. All in the specs. The basic purpose of the form element, as found in the above cited Chapt 17 Form, is The FORM element acts as a container for controls. It specifies: * The layout of the form (given by the contents of the element). * The program that will handle the completed and submitted form (the action attribute). The receiving program must be able to parse name/value pairs in order to make use of them. * The method by which user data will be sent to the server (the method attribute). * A character encoding that must be accepted by the server in order to handle this form (the accept-charset attribute). User agents may advise the user of the value of the accept-charset attribute and/or restrict the user's ability to enter unrecognized characters. A form can contain text and markup (paragraphs, lists, etc.) in addition to form controls. While it is possible that the check-in-check-out is truly a header, it seems unlikely. It feels like a text sizing issue and that should be done through css not mangled headers. I realize you may have no control over that but it seems worth mentioning. drew *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: SPAM-LOW: Re: [WSG] semantics of a simple form
Hi Drew, Thanks for the feedback. The aspx programmer is open to standards and may be receptive to my advice. how about this: fieldset legendRoom Search/legend div class=checkin labelCheck-in Date:/label select name=... option value=101/option /select .. /div div class=checkout label for=...Check-out Date:/label select name=... ./select div class=button input type=submit name=... value=Search id=... / /div /div /fieldset ...allthough when i look at it this nearly feels like a list to me... -best kevin Drew Trusz wrote: While it is possible that the check-in-check-out is truly a header, it seems unlikely. It feels like a text sizing issue and that should be done through css not mangled headers. I realize you may have no control over that but it seems worth mentioning. drew *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] semantics of a simple form
Personally I would say yes, the legend give vital information about what information is being request and the fieldset tells the users/browser/reader that the information with in it is linked together -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of kevin mcmonagle Sent: 25 September 2008 21:29 To: wsg@webstandardsgroup.org Subject: [WSG] semantics of a simple form im not an expert on this but should there be a fieldset or legend around this? not even sure if it qualifies as a form, although it has a submit button. h4Check-in Date:/h4 select name=... option value=101/option . /select select name=... id=... option selected=selected value=09|2008Sep 08/option . /select h4Check-out Date:/h4 select name=... option value=101/option ./select select name=... option selected=selected value=09|2008Sep 08/option . /select div class=button input type=submit name=... value=Search id=... / /div -thanks in advance kevin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.7.2/1689 - Release Date: 24/09/2008 18:51 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] semantics of a simple form
On Sep 25, 2008, at 4:28 PM, kevin mcmonagle wrote: im not an expert on this but should there be a fieldset or legend around this? not even sure if it qualifies as a form, although it has a submit button. h4Check-in Date:/h4 select name=... option value=101/option . /select select name=... id=... option selected=selected value=09|2008Sep 08/option . /select h4Check-out Date:/h4 select name=... option value=101/option ./select select name=... option selected=selected value=09|2008Sep 08/option . /select div class=button input type=submit name=... value=Search id=... / /div -thanks in advance kevin i assume there is a form tag wrapped around this you didn't include? Would obviously require that to qualify as a form. a fieldset is not required for a form to process, but certain doctypes require a fieldset to validate. I always use them as it typically makes the form easier to digest. A legend is not required for any doctype that i know of, but to me, help define the fieldset, rather than using the h4 as you have in your example. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] semantics of a simple form
is an aspx page, theres a form around the whole page, so theres not an individual one around this content block. ok i will use fieldset and legend. -best kevin Todd Budnikas wrote: i assume there is a form tag wrapped around this you didn't include? Would obviously require that to qualify as a form. a fieldset is not required for a form to process, but certain doctypes require a fieldset to validate. I always use them as it typically makes the form easier to digest. A legend is not required for any doctype that i know of, but to me, help define the fieldset, rather than using the h4 as you have in your example. *** 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] ***
