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

Re: All uses of @value

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Mon, 10 Oct 2016 16:34:14 +0200
To: "public-xformsusers@w3.org" <public-xformsusers@w3.org>, "Steven Pemberton" <steven.pemberton@cwi.nl>
Message-ID: <op.yo4f3chhsmjzpq@steven-aspire-s7>
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 Monday, 10 October 2016 14:34:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 10 October 2016 14:34:52 UTC