This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html Multipage: http://www.whatwg.org/C#dom-tree-accessors Complete: http://www.whatwg.org/c#dom-tree-accessors Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/index.html Comment: Clarify that document.links and friends always return the same object Posted from: 81.242.222.5 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0
Checked in as WHATWG revision r8765. Check-in comment: require that document.images and friends always return the same object. This'll be great until either we find that browsers don't always return the same object or until someone notices that this implies that two different Documents will return the same object. http://html5.org/tools/web-apps-tracker?from=8764&to=8765
> this implies that two different Documents will return the same object How so, exactly?
"The same object must be returned each time."; I assume Hixie was being overly pedantic here. (And that's coming from me :).)
Yeah. The wording is the same as in other parts of the spec, and we seem to have interop with those, so I'm leaving it as-is for now.
Yeah, we could throw in something about each time the getter is invoked on with the same Document as "this", I guess...
Or you could use [SameObject] and get this for free from Web IDL (which defines this a little more carefully).
Ok I moved the spec to [SameObject] throughout. The diff below contains this change and others, sorry for mixing them together but they were all part of one editing session.
Checked in as WHATWG revision r8808. Check-in comment: Various editorial IDL changes https://html5.org/tools/web-apps-tracker?from=8807&to=8808