W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

Re: [widgets] features: default value for required

From: Marcos Caceres <marcosc@opera.com>
Date: Tue, 5 Jan 2010 21:15:47 +0100
Message-ID: <b21a10671001051215i4ef259f7o5ccc7b040417de8c@mail.gmail.com>
To: "cyril.concolato" <cyril.concolato@telecom-paristech.fr>
Cc: public-webapps <public-webapps@w3.org>
On Wed, Dec 16, 2009 at 9:50 AM, Cyril Concolato
<cyril.concolato@enst.fr> wrote:
> Hi all,
>
> The algorithm for processing the 'required' attribute is unclear. It says:
> "If a required attribute is used, then let required-feature be the result of
> applying the rule for getting a single attribute value to the required
> attribute. If required-feature is not a valid boolean value, then let the
> value of required-feature be the value 'true'."
>
> I think it misses the case when the required attribute is not used.
> According to the 'Authoring Guideline', it should say:
> "If a required attribute is used, then let required-feature be the result of
> applying the rule for getting a single attribute value to the required
> attribute. *If the required attribute is not used or *if required-feature is
> not a valid boolean value, then let the value of required-feature be the
> value 'true'."
>

I've added the above clarification to the spec. that is, the text "If
the required attribute is not used or"

-- 
Marcos Caceres
http://datadriven.com.au
Received on Tuesday, 5 January 2010 20:16:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:36 GMT