W3C home > Mailing lists > Public > public-xformsusers@w3.org > October 2016

Re: All uses of @value

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Tue, 11 Oct 2016 21:31:22 -0700
Message-ID: <CAAc0PEXQusMRp2EkujFE6Zy2xF9JYTNXxsbbfYp79=GjPBSSJA@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
By the way some children elements are deprecated in favor of AVTs, namely:

- submission/resource
- submission/method
- toggle/case
- setfocus/control
- dispatch/name
- dispatch/targetid
- dispatch/delay
- load/resource

-Erik


On Mon, Oct 10, 2016 at 7:34 AM, Steven Pemberton <steven.pemberton@cwi.nl>
wrote:

> Here is yet a further analysis, while I try to get a handle of all uses of
> @value.
>
> Note that there is a general pattern, which I will illustrate with
> setfocus. In the three different ways of being able to specify the control
> of a setfocus, the priority is:
>
>         <setfocus><control value="'foo'"/></setfocus>
>         <setfocus><control>foo</control></setfocus>
>         <setfocus control="foo"/>
>
> That is to say if you write:
>
>         <setfocus control="A"><control value="'B'">C</control></setfocus>
>
> then control B will be focussed on.
>
> That is: children have precedence over attributes, and @value has
> precedence over content.
>
> In the analysis, I have bolded comments that need discussion.
>
> For instance, there are two cases where an element with @value doesn't
> allow content:
>
>         <function><result>0</result></function>
>         <output><mediatype>text/plain</mediatype></output>
>
> are not allowed.
>
> (Additionally <output>foo</output> is not allowed, but that is possibly a
> special case).
>
> Steven
Received on Wednesday, 12 October 2016 04:32:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 12 October 2016 04:32:11 UTC