Re: Document.createElement: null or HTML namespace?

On 08/10/2014 16:13 , Philippe Le Hegaret wrote:
>> >NB: the spec also claims that XMLDocument.load() is relied upon by
>> >content in the wild. Is that really true? It's broken almost everywhere
>> >and strikes me a particularly useless.
> Did you look to see if we have a test for this?

We have interface tests. They FAIL in anything other than Gecko, though 
of course that could be for other reasons (but I don't believe so in 
this case).

We have a few tests that exercise XMLDocument#load, e.g.:

 
http://w3c-test.org/html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html

and other encoding tests. It doesn't look like we have registered 
results for those tests (running them, I'm guessing it's because they 
time out). Gecko passes, Blink and WebKit fail the XMLDocument#load with 
variants on "undefined is not a function". IE11 doesn't even get that 
far and trips over createDocument() with the third argument dropped (but 
since it doesn't have load() defined on XMLDocument, I don't see how it 
could pass).

-- 
Robin Berjon - http://berjon.com/ - @robinberjon

Received on Wednesday, 8 October 2014 14:59:40 UTC