W3C home > Mailing lists > Public > public-xformsusers@w3.org > April 2012

Re: XPath 2.0: on bindings to atomic values and the result of the element()/attribute() functions

From: Erik Bruchez <ebruchez@gmail.com>
Date: Thu, 5 Apr 2012 10:06:29 -0700
Message-ID: <CAAc0PEX98_OfJarW1WGxT19YJqVR0ppgcVx9U2EA+KsbDdm-4g@mail.gmail.com>
To: "<public-xformsusers@w3.org>" <public-xformsusers@w3.org>
> This one is a bit more difficult, I see the use case of using insert or
> setvalue on the resulting nodes, but I also see users not understanding why
> there values in controls are reset on 'arbitrary' moments in time (in fact
> it will be when the function is re-evaluated, but this might not be on
> every refresh in some implementations).

>  After some more thought I'm no longer strongly against making the
> resulting nodes of the element() and attribute() functions read/write.
> But if we make the resulting nodes read/write, we should at least add a
> note in the spec to warn implementers for this behavior. Maybe even
> encourage implementers to 'log a warning' if a form control is bound to a
> resulting node or a descendant of it.

Just adding an example of what NOT to do with element() is probably enough.

Received on Thursday, 5 April 2012 17:07:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:37:40 UTC