[Bug 22328] HTMLAllCollection.namedItem doesn't match reality

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22328

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|CR                          |

--- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> ---
Behaviors:
1. given an index, zero or one element may be returned
2. given a name, zero or first matching name/id element may be returned
3. given a name, zero, one, or a collection of matching name/id elements may be
returned

(I dusted off an IE6 for this--very nostalgic...)

Test Results: 

API                          Spec  IE6  IE8-IE10  Firefox  Chrome
---------------------------  ----  ---  --------  -------  ------
HTMLCollection.item           1    1&3    1&3       1        1
HTMLCollection.namedItem      2     3      2        2        2*
HTMLAllCollection.item       1&3   1&3    1&3      n/a      1&3
HTMLAllCollection.namedItem  1&3    3      2       n/a       3

*Returns the _last_ matching item for some reason


These are interesting results to say the least. There may be something to say
for splitting the behavior of HTMLAllCollection.namedItem from
HTMLAllCollection.item, as that seems to be what browsers are doing. However,
having what the spec defines is probably *over compatible* which isn't
necessarily a bad thing. Given these results, I don't see a clear motivation to
change the spec at this time. Implementations may still need time to solidify
on the right behavior here, and the spec's current stance seems fine to me.

At this point, I'm removing the CR keyword, as this should definitely not block
the CR spec at this time.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 20 July 2013 00:32:40 UTC