W3C home > Mailing lists > Public > public-xformsusers@w3.org > November 2016

Re: Re-evaluating a switch

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Wed, 9 Nov 2016 09:01:35 -0800
Message-ID: <CAAc0PEUqVnSZBBm5vUt8=E18yzrcgBmoOpRrHMB6sBmyu=LDcg@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
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.

-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 Wednesday, 9 November 2016 17:02:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 November 2016 17:02:29 UTC