W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2013

Re: when will serializing a document throw?

From: Simon Pieters <simonp@opera.com>
Date: Fri, 20 Sep 2013 14:25:58 +0200
To: public-webapps <public-webapps@w3.org>, "Hallvord Steen" <hsteen@mozilla.com>
Message-ID: <op.w3pl5kmxidj3kv@simons-macbook-pro.local>
On Fri, 20 Sep 2013 14:01:36 +0200, Hallvord Steen <hsteen@mozilla.com>  

> If a document is passed to send(), the spec says "re-throw any  
> exception" the serializing throws. There is a test that attempts to test  
> this statement:
> http://w3c-test.org/web-platform-tests/master/XMLHttpRequest/send-entity-body-document-bogus.htm
> It passes a completely empty document without even a document element to  
> send(). No implementation throws.
> Is the incomplete spec attemt on  
> http://domparsing.spec.whatwg.org/#concept-serialize-xml the best  
> reference we have at the moment? Even the statement I found there about  
> serializing comments that do not match the comment syntax seems not to  
> match reality - Gecko serialized a document containing '<html><!--  
> invalid comment ---></html> just fine.

I think the reason here is that what the spec says is the right thing, and  
there probably isn't a Web compat reason not to do the right thing, but  
browsers haven't considered this to be high priority to fix.

Maybe we could remove the throwing from the spec, but it seems kind of sad  
to not catch this in the serializer.

> Does anyone have examples of documents that should and actually DO throw  
> when serialized? Or should we just drop that test and leave that spec  
> statement untested?

Why would you drop the test?

Simon Pieters
Opera Software
Received on Friday, 20 September 2013 12:26:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:13 UTC