[Bug 25582] [DOM-P&S] Two short questions

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25582

--- Comment #2 from Travis Leithead [MSFT] <travil@microsoft.com> ---
On the XMLDocument issue--the idea is not so much which constructor is manifest
by the returned document, but what the "internal" document nature is (and this
is not super-obvious)--whether it (and it's many relevant APIs contingent on
this behavior--not just in this spec) act like an XML document or an HTML
document.

Historically, there was only a "uni-document"--the same document interface used
for all kinds of documents. This simplified things. That is largely how it
works in browsers today, though they will expose an HTMLDocument and
XMLDocument interface for web compat.

I'll need to do a bit of research to see what instance mapping the
parseFromString's document should be associated with.

== 

Regarding text.serializeAsCDATA, this new feature was dropped from this spec in
order to move it along to REC faster. It could be included, but would be marked
'at risk' and removed eventually anyway if two implementations did not support
it.

It may be a candidate for the next edition of this spec if there is still
implementation interest (for it or for a second edition of DOM P&S), and I'd be
happy to re-add it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 6 May 2014 23:06:21 UTC