18195 2012-07-18 17:38:13 +0000 HTMLCollection.prototype.namedItem behavior not defined for HTMLPropertiesCollection 2013-03-17 22:11:37 +0000 1 1 1 Unclassified HTML WG HTML Microdata (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#htmlpropertiescollection-0 P3 normal --- 1 contributor dave.null bzbarsky dzbarsky mike public-html-admin public-html-wg-issue-tracking robin silviapfeiffer1 public-html-bugzilla oldest_to_newest 70856 0 contributor 2012-07-18 17:38:13 +0000 This was was cloned from bug 17201 as part of operation convergence. Originally filed: 2012-05-25 23:23:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-05-25 23:23:42 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html Multipage: http://www.whatwg.org/C#htmlpropertiescollection-0 Complete: http://www.whatwg.org/c#htmlpropertiescollection-0 Comment: HTMLCollection.prototype.namedItem behavior not defined for HTMLPropertiesCollection Posted from: 71.184.125.56 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/15.0 Firefox/15.0a1 ================================================================================ #1 Boris Zbarsky 2012-05-25 23:26:19 +0000 -------------------------------------------------------------------------------- In particular, the spec for HTMLPropertiesCollection says: legacycaller getter PropertyNodeList? namedItem(DOMString name); // overrides inherited namedItem() But the "inherited" namedItem can still be applied to HTMLPropertiesCollection objects, and the behavior of that needs to be defined. HTMLCollection says in an informative note: The namedItem() method returns an object for interfaces that inherit from this interface, which return other objects for historical reasons. and the IDL is: getter object? namedItem(DOMString name); so what you probably want to do here is not override it at all and just say in normative prose that the object returned, if any, is a PropertyNodeList. ================================================================================ #2 Boris Zbarsky 2012-05-25 23:29:36 +0000 -------------------------------------------------------------------------------- Note that the Gecko implementation will be assuming the spec is fixed as I suggest. ================================================================================ 84325 1 silviapfeiffer1 2013-03-13 11:28:14 +0000 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-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/7c5d46081ffeeb4d8c2fe07ed9ec67cf31924f39 Rationale: adopted resolution from WHATWG 84327 2 silviapfeiffer1 2013-03-13 11:29:48 +0000 Gosh, closed wrong bug, sorry! 84328 3 robin 2013-03-13 11:31:18 +0000 Hahaha :) I'm making it ASSIGNED rather than REOPENED since the latter has a specific meaning. 84535 4 silviapfeiffer1 2013-03-17 22:11:37 +0000 Assigning to correct component. 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-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/82c990a7ef7b7c71ecf5aa739388fbacf8adc898 Rationale: Accepted WHATWG resolution, see bug 17201 . Instead of overriding namedItem() calls, shadow them, so both HTMLCollection.prototype.namedItem and HTMLCollection.namedItem work. Closes W3C bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=18195 Also note: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17161 for removal of legacycaller from HTMLPropertiesCollection.