- From: ArkadiuszMichalski <notifications@github.com>
- Date: Mon, 28 Dec 2015 12:30:19 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Message-ID: <whatwg/dom/issues/137/167647934@github.com>
Now it's clear, constructor Document() return new Document object (it's still XML document so internal state is "xml", what is default value and we don't need to mention about this). Remember that document has default value for its internal state and if they are not change (when we construct this document) then DOM (or other spec) don't need mention about it every time (https://dom.spec.whatwg.org/#concept-document-base-url). Firefox supports this constructor in correct way: https://bugzilla.mozilla.org/show_bug.cgi?id=1017932 HTML spec (and some other spec) add next stuff for Document interface and they are available for all documents (HTML/XHTML/XML) but it doesn't mean you can use all of them in all documents without any problem. Please try analize document.write method (https://html.spec.whatwg.org/multipage/webappapis.html#dom-document-write) , when you invoke this method in XML document then you get error, but this method still exist in Document object. What actually interfaces are returned by the browsers when we using various constructing methods is known bug (still under consideration in which direction to go further with this): https://www.w3.org/Bugs/Public/show_bug.cgi?id=22960 << W3C bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=22960#c5 << Chrome started to do something in this direction but it is still a long road to full compliance with the all specifications. https://bugzilla.mozilla.org/show_bug.cgi?id=897815 << Gecko bug --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/137#issuecomment-167647934
Received on Monday, 28 December 2015 20:30:48 UTC