W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2014

Test 530

From: David Junger <tffy@free.fr>
Date: Mon, 31 Mar 2014 19:32:23 +0200
Message-Id: <D7ABB6BA-3851-4C80-8F65-E6995A543722@free.fr>
To: Voice Public List <www-voice@w3.org>
Test 530 is malformed XML because of unmatched closing tags in a <assign> content. That may be intended to cause an error, but it causes a parsing error when the whole file is loaded, NOT when <content> is evaluated. The whole test crashes before it can even start running.

And any non-fatal error in inline <assign>, e.g. malformed JSON or malformed but escaped XML, will cause the interpreter to silently fall back to reading it as space-normalized text, according to the current requirements.

If you want to write an <assign> that doesn't assign, you have to use <assign expr> with a bad expr value.

Inline content will never fail, unless you add the optional type attribute, whose behavior hasn't been specified but which we might define in a way that malformed content will raise an error rather than fall back.

Received on Monday, 31 March 2014 17:32:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:04:01 UTC