This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9278 - "...with the same argument, the user agent **may** return the same object as the object returned by the earlier call.": Make this a must. To quote hsivonen, "The Web leaves no edge case unexercised."
Summary: "...with the same argument, the user agent **may** return the same object as ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-18 20:29 UTC by contributor
Modified: 2010-10-04 14:29 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-03-18 20:29:55 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#dom-tree-accessors

Comment:
"...with the same argument, the user agent **may** return the same object as
the object returned by the earlier call.": Make this a must. To quote
hsivonen, "The Web leaves no edge case unexercised."

Posted from: 91.182.128.168 by ms2ger@gmail.com
Comment 1 Ian 'Hixie' Hickson 2010-03-31 20:30:51 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: While I really wish we could require that, browser vendors won't implement it (because it requires unbounded caching) and the alternative (never caching) isn't performant enough to be competitive with some existing browsers (which cache). So unfortunately we're stuck in this annoying middle-ground.