W3C home > Mailing lists > Public > public-xformsusers@w3.org > April 2018

Issues with respect to <output/> mixed content.

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Thu, 19 Apr 2018 16:05:12 +0200
To: " XForms" <public-xformsusers@w3.org>
Message-ID: <op.zhp1eyltsmjzpq@steven-xps>
We're trying to unify

since their effect is essentially the same (make some information  
available to the user), and the only difference is *when* they do that.

So we have unified them as far as possible, the main differences being:

* only <output/> may have <label/>, <help/>, <hint/>, and <alert/>  
* <label/>, <help/>, <hint/>, and <alert/> may have mixed content  
(including <output/> elements, as well as host-language elements)

	<input ref="claim">
	    <label>Claim for the year <output ref="../year"/></label>

has identical effect to
	<label value="'Year'"/>
there is obvious advantage to allowing the former.

In the definition of @value we have the text "If the element has PCDATA  
content, then the result of the expression overrides that content."
What we don't have is "if the element has a value attribute, you may use  
element content instead."

So you can have
	<label value="'Year'"/> and <label>Year</label>
	<output value="'Year'"/>
but not

Should we add that possibility?

Advantage: consistency

But: Do we want to allow
	<output>Claim for the year <output ref="../year"/></output>
as well?

And: we allow
	<label>Some <i>stuff</i>.</label>
Should we also allow:
	<output>Some <i>stuff</i>.</output>

(It is worth noting that this *is* currently already allowed:

    <label>Some <i>stuff</i> with <output value="answer"><label>The  
answer</label><alert>Must be integer</alert></output>.</label>


Received on Thursday, 19 April 2018 14:05:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:37:49 UTC