148880 2015-09-04 20:33:46 -0700 HTMLOptionsCollection.namedItem should return a NodeList when there are multiple matching nodes 2016-10-12 12:55:36 -0700 1 1 1 Unclassified WebKit Forms WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED InRadar P2 Normal --- 1 rniwa krollin cdumez krollin webkit-bug-importer oldest_to_newest 1123848 0 rniwa 2015-09-04 20:33:46 -0700 See https://html.spec.whatwg.org/multipage/infrastructure.html#htmloptionscollection Unlike named getters, we must return a NodeList that contain the list of all matching nodes in HTMLOptionCollection.namedItem. 1123849 1 rniwa 2015-09-04 20:34:23 -0700 This bug was found by the newly added test: LayoutTests/http/tests/w3c/html/semantics/forms/the-select-element/common-HTMLOptionsCollection-namedItem.html 1123850 2 webkit-bug-importer 2015-09-04 20:34:25 -0700 <rdar://problem/22590497> 1133144 3 cdumez 2015-10-14 09:52:12 -0700 Where is this in the spec? The IDL says namedItem() returns an Element. And there is this comment: """ element = collection . namedItem(name) element = collection[name] Returns the item with ID or name name from the collection. If there are multiple matching items, then the first is returned. """ Therefore, the spec seems to indicate we should NOT return a NodeList. Maybe it is a bug in the test? 1133173 4 krollin 2015-10-14 10:45:39 -0700 I've filed a w3c-test bug: https://github.com/w3c/web-platform-tests/issues/2255 1139033 5 krollin 2015-11-03 12:48:23 -0800 I've submitted a patch to the test and create a pull-request: https://github.com/w3c/web-platform-tests/pull/2302 1239438 6 krollin 2016-10-12 12:55:36 -0700 Merged and closed (back in February).