Talk:DOM:document
From MDC
Contents |
[edit] Page layout
I'm just messing around with different page layout ideas...don't assume that anything here is final for the time being dria 05:42, 15 Jun 2005 (PDT)
- If people like this work-in-progress layout, based on the table layout of "DOM:element", feel free to use it for the "Properties" section here. It includes six of the seven new properties covered by W3C DOM 3 which appear to be supported by Gecko (at least "typeof" returns something besides "undefined" for six of them). I omitted one DOM 3 document property,
document.domConfig, because currently Gecko (Gecko/2007082805) throws an uncaught exception in the error console for it (bug 226193#c4 says this is currently the correct behavior, since it's not implemented but it will be eventually) --George3 20:24, 3 September 2007 (PDT)
- From a quick skim of your version, it seems like a definite improvement over what we have now. I do think we should use a unified format for all the 'topic' pages, perhaps start a discussion in dev-mdc for the points where you don't agree with jresig's format (DOM:element)? --Nickolay 12:08, 9 September 2007 (PDT)
[edit] document.contentWindow
This is a property of frame elements, not documents. See bug 228497. --Maian 09:57, 15 October 2005 (PDT)
Should there be a separate section for frame (and iframe) elements that includes things like .contentWindow and .contentDocument?
Should there be separate sections for other types of elements as well? More information is good, but clutter is bad. Thoughts? --Jonnyq
- There should be separate pages for each HTML elements. I'm not sure what the naming scheme should be, but since we're probably going to use interface names, I'd put it on DOM:HTMLFrameElement and DOM:HTMLIFrameElement. --Maian 20:00, 17 October 2005 (PDT)
[edit] createAttribute
This is a mess. createAttribute is indeed a method of the Document object, and NOT element objects. createAttribute creates an anonymouse attribute node that can later be appended to an element via element.setAttributeNode. This should be fixed (it was screwy on the old reference, too). Strike that. I see that it's been fixed up. I changed the text and link on the page to read correctly. --Jonnyq 15:09, 17 October 2005 (PDT)
[edit] createElementNS
this link points to createElement, and has no content of it's own.
found this link: http://www.zend.com/manual/function.dom-domdocument-createelementns.php
Looking under the recent 250 changes for the last 7 days, there is a createElementNS page that has plenty of content.
The URL is:
http://developer.mozilla.org/en/docs/DOM:document.createElementNS
Sorry about that monkey! I have updated the link to point to that page now.
[edit] Getting a reference to a new Document object
Is there a way to do that, without using a Window object? Basicly what I want to do is to get the -Document- of a certain URL and check some stuff about some of its elements. I need to do it several times, and I don't need to display anything. Is there a way to accomplish that without having to display the content of each new document in the same window (or a new one)? (Sorry if it's not the right place to ask that...) Yuval25 21:30, 7 February 2007 (PST)
- Yes, this is the wrong place to ask that, developer newsgroups are for discussion. This has been asked many times though, see Parsing HTML From Chrome. --Nickolay 06:43, 9 February 2007 (PST)
[edit] Monitor charset support
Gecko currently supports document.characterSet but not, other (mostly nonstandard?) variations (charset, defaultCharset, actualEncoding) which IE and Safari/Webkit happen to implement (see WebKit bug). If they ever get implemented by Gecko, they'd belong on this page --George3 20:24, 3 September 2007 (PDT)