W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

Re: Comments on the http://www.w3.org/TR/widgets/

From: Marcos Caceres <marcosc@opera.com>
Date: Tue, 2 Nov 2010 15:50:31 +0100
Message-ID: <AANLkTimC+kbFuc03GGDiNmuHdheB5wems5LfyC=BdY6n@mail.gmail.com>
To: viji <viji@borqs.com>
Cc: public-webapps@w3.org
On Tue, Nov 2, 2010 at 9:36 AM, viji <viji@borqs.com> wrote:
> Hello Marcos
>   The changes for "Email attribute" and "Rule for Getting Text Content with
> Normalized White Space" seem fine.

Good to hear!

>  I have a comment on usage of Global attributes for Icon, Feature, Content
> and Param elements.
>  For all these elements dir attribute does not make sense. The text you
> added contains the line " What effect specifying a global attribute has on
> an elements is determined by Step 7 of this specification."
>  In step 7, the reference is given to Rule for Getting Text Content or rule
> for getting a single attribute value  etc. Does this clarify as to whether
> dir attribute is applicable or not for the elements like Icon, Feature,
> Content and Param elements.

Yes, these rules hopefully make it clear how and when dir and xml:lang
are taken into consideration. You will notice that the rule for
parsing a non-negative number does not take dir or xml:lang into


While the Rule for Getting Text Content always returns a localizable string:

Please do take a look and see if the rules make sense.

The reason we leave the global attributes there is for
forward/backwards compatibility in case we want to add human readable
text in the future. Consider this hypothetical example:

<feature name="some:feature" dir="ltr">
   <otherns:role xml:lang="en">This feature is needed to do something

Marcos Caceres
Opera Software ASA, http://www.opera.com/
Received on Tuesday, 2 November 2010 14:51:25 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:28 UTC