If I hook up a send to an xforms-select on a xforms:select1, it only triggers the submission the first time. On subsequent selects I get this error: Error: elm.parentNode has no properties Source File: chrome://xforms/content/select1.xml Line: 942
Possibly a dupe of 332292?
Created attachment 223042 [details] [diff] [review] Crude fix Aparently the selected element does not always have a parent node? Checking for that makes the dispatchEvent() work. It does not fix the testcase 100%, because the xforms-select event is sent before the node value is changed, so the result gotten from the server is "lagging". But it might be correct event sequencing? Dunno.
Comment on attachment 223042 [details] [diff] [review] Crude fix ugh, you really should figure out why elm has no parentNode - you probably have a reference to an element no longer in the DOM. Check is ok for a temp fix though (0.6)
Comment on attachment 223042 [details] [diff] [review] Crude fix something's wrong alright, but temp fix. for 0.6, please.
Comment on attachment 223042 [details] [diff] [review] Crude fix Could you put the whole method inside CDATA. & is just too ugly, & is much better With that r=me
Fixed on trunk w/smaug's comment fixed
Filed follow up bug 339062.