- From: Ronald van Kuijk <rvkuijk@intercommit.nl>
- Date: Thu, 02 Sep 2010 23:50:28 +0200
- To: www-forms@w3.org
- Message-ID: <20100902215028.4a10ee96@mail.intercommit.nl>
@, I've been reading the spec with regard to the xforms-out-of-range event and cannot get a clear picture on how to respond to this event. In the spec it says nothing about a select control receiving this event being either still valid or invalid. An empty string (e.g. the default) can be valid according to the xsd that is behind it and even according to the constraint. So the control is then valid but out of range, correct? Personally I'd say the visual response to this should be to render the control as being invalid, so the out-of-range taking precedence. Theoretically it could also be the other way around. The control being invalid according to e.g. a constraint, but being in range. Since you (hope to) have other choices in the select, you could probably make it valid by selecting another item, so in this case the invalidness of the control takes precedence. This is just how I would interpret things, so if someone from the wg could confirm this or describe the correct behaviour, that would be great. Cheers, Ronald
Received on Thursday, 2 September 2010 21:51:00 UTC