Re: [whatwg] CDATA and RCDATA restrictions don't always trigger a parse error

2007-06-22 Thread Ian Hickson
On Wed, 20 Jun 2007, Anne van Kesteren wrote: Currently CDATA and RCDATA are required not to contain the string /script for instance if the start tag is script. However, the following does not trigger a parse error: script!-- /script --/script yet it is non-conforming. Given that

[whatwg] CDATA and RCDATA restrictions don't always trigger a parse error

2007-06-20 Thread Anne van Kesteren
Currently CDATA and RCDATA are required not to contain the string /script for instance if the start tag is script. However, the following does not trigger a parse error: script!-- /script --/script yet it is non-conforming. Given that conformance checkers are required to follow the

Re: [whatwg] CDATA and RCDATA restrictions don't always trigger a parse error

2007-06-20 Thread Henri Sivonen
On Jun 20, 2007, at 14:48, Anne van Kesteren wrote: Currently CDATA and RCDATA are required not to contain the string / script for instance if the start tag is script. However, the following does not trigger a parse error: script!-- /script --/script yet it is non-conforming. Given that

Re: [whatwg] CDATA and RCDATA restrictions don't always trigger a parse error

2007-06-20 Thread Ian Hickson
On Wed, 20 Jun 2007, Henri Sivonen wrote: On Jun 20, 2007, at 14:48, Anne van Kesteren wrote: Currently CDATA and RCDATA are required not to contain the string /script for instance if the start tag is script. However, the following does not trigger a parse error: script!-- /script

Re: [whatwg] CDATA and RCDATA restrictions don't always trigger a parse error

2007-06-20 Thread Simon Pieters
On Wed, 20 Jun 2007 22:31:37 +0200, Henri Sivonen [EMAIL PROTECTED] wrote: On Jun 20, 2007, at 14:48, Anne van Kesteren wrote: Currently CDATA and RCDATA are required not to contain the string / script for instance if the start tag is script. However, the following does not trigger a parse