- From: Leigh L. Klotz, Jr. <Leigh.Klotz@xerox.com>
- Date: Wed, 31 Aug 2011 11:46:01 -0700
- To: "Leigh L. Klotz, Jr." <Leigh.Klotz@xerox.com>
- Cc: public-forms@w3.org, ebruchez@orbeon.com
Erik, In re http://lists.w3.org/Archives/Public/public-forms/2010Jan/0037.html > 2. xforms.trigger.content, and many other places > > This requires that xforms.label precedes xforms.UI.Common.content. > Do we really want to enforce that the label is first? E.g. shouldn't > this be valid: > > <xforms:trigger> > <xforms:setvalue ev:event="DOMActivate" .../> > <xforms:label>Click me</xforms:label> > </xforms:trigger> The prose says it must be first and would be difficult to change at this point. John Boyer suggests that when we change label to be specified either as a child element or remotely in label/@for, we consider allowing label at any spot in control children. Leigh.
Received on Wednesday, 31 August 2011 18:46:25 UTC