xforms-compute-exception does not immediately halt processing.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open http://ubiquity-xforms.googlecode.com/svn/trunk/testsuite/W3C-
XForms-1.1/Edition1/Chapt07/7.5/7.5.a.xhtml

What is the expected output? What do you see instead?

Three xforms-compute-exception messages appear.  One for each element in 
the bind nodeset over which the invalid computed expression is being 
applied.

The prose of the test implies that only one message should appear.

I can't say for certain whether the behaviour of UXF, or the test prose is 
erroneous.

Note: 
The Selenium driver <http://ubiquity-
xforms.googlecode.com/svn/trunk/testsuite/W3C-XForms-
1.1/Edition1/driverPages/SeleniumTests/Chapt07/7.5/7.5.a.html> will 
register a pass, as it does not require all messages to be dismissed prior 
to declaring the test complete.  

Original issue reported on code.google.com by paul.but...@gmail.com on 26 Feb 2009 at 5:04

[GoogleCodeExporter]

I don't think this is explicitly specified in the XForms spec, but I don't 
think UXF
behavior is wrong. 

Original comment by nick.van...@gmail.com on 6 Mar 2009 at 7:24

[GoogleCodeExporter]

Closing this issue as invalid, as per Nick's comment above.

Original comment by phil.boo...@gtempaccount.com on 7 Mar 2009 at 11:48

• Changed state: Invalid