W3C home > Mailing lists > Public > public-pfwg-comments@w3.org > April to June 2009

Empty containers not allowed

From: Henri Sivonen <hsivonen@iki.fi>
Date: Tue, 14 Apr 2009 13:52:15 +0300
Message-Id: <22956187-C580-43D9-A86B-711B7E897FD1@iki.fi>
To: public-pfwg-comments@w3.org
> Note: When multiple roles are specified as "Required Child Elements"  
> for a role, at least one instance of one required child element is  
> required. This specification does not require an instance of each of  
> the listed child roles. For example, a menu should have at least one  
> instance of a menuitem, menuitemcheckbox, or menuitemradio. The menu  
> role does not require one instance of each.

Why aren't empty containers allowed? Empty containers might arise from  
natural application states, and putting placeholders in containers  
just complicates things.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Tuesday, 14 April 2009 10:53:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 14 April 2009 10:53:00 GMT