W3C home > Mailing lists > Public > public-forms@w3.org > August 2011

Model driven switch

From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
Date: Tue, 30 Aug 2011 14:25:25 +0000
To: Public Forms <public-forms@w3.org>
CC: John Boyer <boyerj@ca.ibm.com>
Message-ID: <FF7897A9-7B48-4F35-90E5-DCFE419B57F6@inventivegroup.com>
Hi John,

The tekst looks good, I have a couple questions/remarks about border cases though ;)

* What happens when the string value of the caseref doesn't matches a case (initially or after an set value), the spec says that the first case is then selected, but is the value in the model then also updated accordingly?
** Are there any forms-value-change events targeted to the switch if the caseref value changes (and other events) I don't think this will be the case.
** What if the node the caseref  points to isn't relevant or doesn't exists, how does the model driven switch keeps track of its state (I would have expected that when using the caseref attribute, the node it points to replaces the implicit node used by ui driven switch)

Kind regards,

Nick Van den Bleeken
R&D Manager

Phone: +32 3 821 01 70
Office fax: +32 3 821 01 71



Inventive Designers' Email Disclaimer:

(image/png attachment: image001.png)

(image/png attachment: image002.png)

(image/png attachment: image003.png)

Received on Tuesday, 30 August 2011 14:25:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:05 UTC