Dear WG, Is there a compelling reason for the provision that xforms-disabled/enabled event cannot target repeat (4.4.1 -4.4.11) and repeat control cannot be relevant or non-relevant (8.1.1)? Perhaps a repeat can become non-relevant'(relevant) and the xforms-disabled (enabled ) fire when it does not have any (has at least one) relevant repeat items (item)? And a couple of minor issues: 1. Typo in 8.1.1: Second bullet: ... Note: Form controls that read or write simpleContent produce this exception whenever and as soon as they are bound to an element node that an element child node. 2. The very first link: (not terribly useful ;) http://www.w3.org/TR/2009/CR-xforms11-20090311/ does not work. Regards, Vlad Trakhtenberg.Received on Friday, 13 March 2009 00:15:01 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 13 March 2009 00:15:02 GMT