W3C home > Mailing lists > Public > www-forms@w3.org > March 2008

Re: what should happen when a xf:insert is inside a xforms-select handler?

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Tue, 4 Mar 2008 22:17:34 -0800
Message-Id: <11654CD6-2886-435B-8B80-933BB9760277@orbeon.com>
To: www-forms@w3.org

> I get that the net result to a form author is that, at the time the  
> xforms-select occurs, the node value of the bound node may be the  
> old value or the new value, depending on why the xforms-select is  
> happening.


> Hence, it is possible in all cases to tell whether bound data node  
> has the same value as the selected item, should you wish to only do  
> something if they differ or if they are the same.

I think that this is an acceptable workaround for now, unless changing  
the order of events in the case of user selection is a trivial change,  
which it sounds like it isn't.

> Realizing that the above may not win the convenience award, it  
> would, for anyone who responded to the call for expression of need,  
> cause me to ask:  what specifically are you trying to do that you  
> can't do?

I don't have a strong use case. I was reacting to the inconsistency- 
with-a-reason, from the point of view of the event handler. If there  
is a reasonable fix, we should do it, otherwise, we'll have to live  
with it.

Ultimately, I do think we need to add proper context information to  
all events. It just seems reasonable that if you say that "something"  
got selected, there is a way within the event of determining what the  
something is, so that you don't have a strong constraint about where  
to place your event handler. But that is a question for another thread  


Orbeon Forms - Web Forms for the Enterprise Done the Right Way
Received on Wednesday, 5 March 2008 06:17:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:21 UTC