W3C home > Mailing lists > Public > www-forms@w3.org > September 2006

Re: xforms-value-changed

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Fri, 22 Sep 2006 11:49:00 +0100
Message-ID: <640dd5060609220349v7eba27e2m33b292a97d840162@mail.gmail.com>
To: www-forms@w3.org

Hi Victor,

I think this is a good idea. More recently we've started to add
information about what should be set in the DOM 2 Events object when
events are fired, and we have the event() XPath function which allows
us to get to this. With this framework it shouldn't be too difficult
to do what you are suggesting.

(As to when it could be done and in which specification, I'll defer to John! :)

Regards,

Mark

On 21/09/06, Victor Bolshov <crocodile2u@yandex.ru> wrote:
>
> Hello everybody!
>
> Recently, I came upon a thing I could't implement in my form without a
> hack-like trick.
>
> I have a <setvalue event="xforms-value-changed"> element nested in
> <select1> (well, actually, the type of control doesn't matter). When
> setting the value, I need to know both values: the one that element had
> *before* the change happened - and the one it has *after* change.
>
> I believe this feature could be useful to many. Possibly, the spec lacks
> something?
>
> I can provide an example of what I am doing - to be more clear.
>
> Regards, Victor.
>
>
>
>


-- 
Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
http://www.formsPlayer.com/
Received on Friday, 22 September 2006 10:49:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:06 GMT