- From: Klotz, Leigh <Leigh.Klotz@xerox.com>
- Date: Tue, 15 Jun 2010 10:25:54 -0700
- To: <public-forms@w3.org>
- Cc: "support xsltforms" <xsltforms-support@lists.sourceforge.net>
According to http://www.w3.org/TR/xforms11/#sequence-for-input xf:input change the value until you navigate off, unless you use incremental="true". If the bound node is of type xsd:boolean, however, most desktop browser XForms processors will render the control as a checkbox. So, if you check the checkbox, nothing happens until you navigate off. I've not seen implementations with the behavior that checkboxes don't work until you tab off before, but now xsltforms is exhibiting it. A quick read of the XForms 1.1 Rec shows that it may be the spec-correct behavior. We had a similar situation with select1, and we fixed it by saying that the default value of attribute incremental for select1 is true: http://www.w3.org/TR/xforms11/#sequence-for-select1 How can we fix it for input bound to boolean? It doesn't seem like we can easily say that the default value of attribute incremental for input bound to boolean is true. Authors might not know whether a control is bound to a boolean or not; for example, now that we allow non-homogeneous repeats: <repeat nodeset="*"><input ref="value"><label ref="../label"></label></input> Leigh.
Received on Tuesday, 15 June 2010 17:26:34 UTC