PUBLIC MARKS with tags QA & safari

# The lines output by Curly Logo weren’t being broken, everything was stuck together on one line. Turns out Firefox was letting me get away with creating (XHTML) p nodes by using “document.createElement” whereas I should really be using the XML approved “document.createElementNS” to create nodes from the XHTML namespace. So now I do.

Quoi ? Les gens corrigent leurs outils quand le navigateur est strict. Les fabricants de navigateurs nous auraient-ils menti ;)

Safari: 200s. Firefox: 304s. Safari wrong. Firefox right. Safari slooooowwwww. Firefox fast.

Very informative list to know what's going on.

"A lot of the DOM Level 2 Core tests are not available in HTML standalone versions yet - we’re working with the W3 Consorium’s QA working group on this."