kangax / jstests Goto Github PK

http://kangax.github.com/jstests/etago_delimiter_test/

The full algorithm is described in the HTML spec here and here, but it’s a little hard to read IMHO :)

Anyhow, HTML5^​H now finally standardized the behavior that all browsers implemented in the first place (in spite of what HTML 4.01 prescribed):

1. This works — the alert message will be shown:

   <script>document.write('<p></p>'); alert(1);</script>

2. This will prematurely close the <script> element — the alert message won’t be shown:

   <script>document.write('<script></script>'); alert(1);</script>

Again, this is how it has always worked in every browser (as your test case states).

It might be worth updating the page to mention that HTML5^​H standardizes what you already discovered, i.e. that only the </script sequence will terminate the <script> element’s content (depending on the next character), and other </ sequences are fine and safe to use.

See #whatwg chat logs: http://krijnhoetmer.nl/irc-logs/whatwg/20110326#l-353

Update: I’ve published a much more detailed write-up including some interesting (IMHO) edge cases on my blog: http://mathiasbynens.be/notes/etago

Firefox 45 (next nightly train, should be built sometime today according to the calendar) has finally implemented innerText. It would be pretty cool to see what differences it has with current implementations.