Bug 13112 - Many differences between Safari, IE, and FF when accessing elements in DOM collections
Summary: Many differences between Safari, IE, and FF when accessing elements in DOM co...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-18 15:11 PDT by Geoffrey Garen
Modified: 2022-07-19 11:36 PDT (History)
4 users (show)

See Also:


Attachments
testcase for null-like arguments (1.20 KB, text/html)
2007-03-18 15:12 PDT, Geoffrey Garen
no flags Details
test case for numeric arguments (1.25 KB, text/html)
2007-03-18 15:12 PDT, Geoffrey Garen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Geoffrey Garen 2007-03-18 15:11:42 PDT
Broken off from bug 13106.

A few key questions:
1. What counts as a number (leading/trailing junk, hexadecimal, non-integer, etc.)?
2. Should collection(argument) match collection[argument] or collection.item(argument), or should all three match?
3. Should collection.item() handle two arguments or only 1?
4. Should collection.item(argument) return null or undefined when argument is not found?
Comment 1 Geoffrey Garen 2007-03-18 15:12:23 PDT
Created attachment 13696 [details]
testcase for null-like arguments
Comment 2 Geoffrey Garen 2007-03-18 15:12:50 PDT
Created attachment 13697 [details]
test case for numeric arguments
Comment 3 Geoffrey Garen 2007-03-18 15:13:48 PDT
We need to write a test for question 3. I think the rest are covered.
Comment 4 Ahmad Saleem 2022-07-19 10:46:20 PDT
Safari 15.5 on macOS 12.4 matches with other browsers (Firefox Nightly 104 and Chrome Canary 105) in the attached test cases. I think they were fixed along the way and this bug can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks!
Comment 5 Ryosuke Niwa 2022-07-19 11:36:51 PDT
Oh yeah, we improved this area some time ago.