Re: setvalue on a nodeset

I've had this wish as well. There is no really good reason to apply the
first node rule here, especially now that `ref` no longer implies a single
node.

Changing this would break backward compatibility of course. You could
introduce an attribute:

  <setvalue ref="a[condition]" value="..." all="true"/>

but that looks a bit awkward.

A workaround is to write:

  <setvalue iterate="a" ref="." value="..."/>

-Erik



On Sun, Sep 24, 2017 at 4:41 AM, Steven Pemberton <steven.pemberton@cwi.nl>
wrote:

> I find myself today with a form where in three places I want
>
>    <setvalue ref="a[condition]" value="..."/>
>
> to set *all* matching nodes.
>
> Steven
>
>