- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Thu, 10 Nov 2016 11:01:30 +0100
- To: "Erik Bruchez" <ebruchez@orbeon.com>
- Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Received on Thursday, 10 November 2016 10:02:12 UTC
On Wed, 09 Nov 2016 18:01:35 +0100, Erik Bruchez <ebruchez@orbeon.com> wrote: > I would argue the following: > > If there is no `@name` attribute, `<switch>` simply doesn't read/write a > value via its binding at all (the binding can still impact relevance). > > So a `<setvalue>` does not have any effect on the selected case in your > example. True, but the control would get an xforms-value-changed, so it could be argued, that the response to a value changed is to activate the switch evaluation, which would result in the "selected" node being selected. Steven > > -Erik > > On Wed, Nov 9, 2016 at 7:26 AM, Steven Pemberton > <steven.pemberton@cwi.nl> wrote: >> This is about XForms 1.1 behaviour. >> >> <switch ref="foo"> >> <case id="a">...</case> >> <case id="b" selected="true">...</case> >> </switch> >> >> Initially b is selected. >> >> Then I do <toggle case="a"/>. >> >> So now a is selected. >> >> Then I do <setvalue ref="foo">bar</setvalue> >> >> I am assuming that b gets reselected. >> >> Do we agree? >> >> Steven
Received on Thursday, 10 November 2016 10:02:12 UTC