- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Fri, 23 Apr 2021 10:16:55 +0000
- To: Alain Couthures <alain.couthures@agencexml.com>, public-xformsusers@w3.org
Received on Friday, 23 April 2021 10:17:10 UTC
This sounds like a good plan. What is it exactly that fails with the comparisons? Steven On Thursday 22 April 2021 09:10:18 (+02:00), Alain Couthures wrote: Hello, The main form of the testsuite does not currently work well with XPath 2.0+ (with Compatibility Mode set to false) because of default text comparisons even with numeric values. This is a well-documented difference with XPath 1.0: https://www.w3.org/TR/xpath20/#id-incompat-in-false-mode Adding an explicit number() function call in expressions sounds like a good compatibility solution for both XPath 1.0 and XPath 2.0+ engines: “. > ../count” to be replaced with “number(.) > number(../count)” It might be interesting to add a mention to this in XForms 2.0 specifications. What do you think? --Alain
Received on Friday, 23 April 2021 10:17:10 UTC