Sicking and I were talking about this.... We feel that the fact that documents created via DOMImplementation are not data until you document.load() into them is weird. The proposal we have is: 1) All (XML?) documents start off as data at construction time. 2) Calling StartDocumentLoad toggles the state of the document as needed. 3) XMLDocument::Load just uses the current state, whatever it is. 4) There is no api other than StartDocumentLoad to control data/nondata state for now. Thoughts? I can do this if we think it's the right approach. The behavior for document.load into "live" (in a docshell) documents will change, but I think that's what we want... (Note to self: logic in XMLDocument::StartDocumentLoad needs to be fixed to handle repeated calls to that method -- some booleans are set to true only, never false, right now).
12 years ago