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

Hi Aaron,

I'd like to see the thing which doesn't work.

One does not have direct tree comparison capabilities, regardless of event 
order, and it doesn't seem to matter much because the subtrees will often 
be keyed by the value of a particular element in the subtree anyway...

Thanks,
John M. Boyer, Ph.D.
Senior Technical Staff Member
Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw





Aaron Reed <aaronr@us.ibm.com> 
Sent by: www-forms-request@w3.org
03/05/2008 09:00 AM

To
www-forms@w3.org
cc

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







Hey John,


> 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?
> 

Your workaround will work for cases where the xf:item contains xf:value 
elements.  But I do not believe that the workaround is possible should 
the xf:itemset contain a xf:copy element unless there is an xpath 
function that I'm unaware of (a distinct possibility) to determine node 
tree equality.  I guess it is possible using JS, though (on Firefox, at 
least).

--Aaron