W3C home > Mailing lists > Public > w3c-wai-hc@w3.org > October to December 1997

Discrepancy between OPTION proposal and current DTD Draft

From: MegaZone <megazone@livingston.com>
Date: Wed, 29 Oct 1997 06:36:45 -0800 (PST)
Message-Id: <199710291436.GAA07185@server.livingston.com>
To: w3c-wai-hc@w3.org, w3c-html-wg@w3.org
Proposal:

<!ELEMENT OPTGROUP - - (OPTGROUP|OPTION)+ -- grouping for OPTION -->
<!ATTLIST OPTGROUP
  %attrs;                          -- %coreattrs, %i18n, %events --
  disabled  (disabled)   #IMPLIED  -- control is unavailable in this context --
  label       CDATA      #REQUIRED -- for user in hierarchical menus --
  >

Draft:

<!ELEMENT OPTGROUP - - (OPTGROUP|OPTION)+ -- option group -->
<!ATTLIST OPTGROUP
  %attrs;                          -- %coreattrs, %i18n, %events --
  disabled  (disabled)   #IMPLIED  -- control is unavailable in this context --
  label       CDATA      #IMPLIED  -- for use in hierarchical menus --
  >


The WAI HC has label #REQUIRED on OPTGROUP, the draft has it IMPLIED.

Remember, OPTGROUP doesn't have any normal text associated with it.  The
context/grouping is provided by the label.  At least as we'd envisioned it.

Label is #IMPLIED on OPTION - it falls back to element content as it
always has.  But OPTGROUP doesn't have this fall back.

Is there value in grouping for the sake of grouping with no label?  What
is the implied value?

-MZ
--
Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 4464 Willow Road, Pleasanton, CA 94588
Received on Wednesday, 29 October 1997 09:45:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:56:11 UTC