- From: Gavin Kistner <phrogz@me.com>
- Date: Mon, 30 Jun 2014 22:37:23 +0000 (GMT)
- To: David Junger <tffy@free.fr>
- Cc: "www-voice@w3.org (www-voice@w3.org)" <www-voice@w3.org>
Received on Monday, 30 June 2014 22:37:52 UTC
On Jun 30, 2014, at 08:30 AM, David Junger <tffy@free.fr> wrote: Le 30 jun 2014 à 15:53, Jim Barnett <1jhbarnett@gmail.com > a écrit : > What would happen in test 179, where we have conf:eventDataVal="123"? Would it be a problem to quote that in ECMA? Not at all. A number is equivalent (==) to its string representation in ECMAScript. While this is true (and often convenient) I would suggest that it would be a bad idea to have the ECMAScript tests rely on loose equality. Since ""==0, and and 0==false, and false==[], such a test could (theoretically) provide false positive passes. I remember that you all had a discussion on === in the XSLT tests a while back, so I assume there's a reason that you kept with == in the XSLT. I'll not re-open that can of worms. I'll just say that since we have conf:eventDataVal--allowing the XSLT to determine how to best represent the test for the data model--then we should also have <conf:content> so that the XSLT can translate the intention the same way.
Received on Monday, 30 June 2014 22:37:52 UTC