WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED CONFIGURATION CHANGED
13112
Many differences between Safari, IE, and FF when accessing elements in DOM collections
https://bugs.webkit.org/show_bug.cgi?id=13112
Summary
Many differences between Safari, IE, and FF when accessing elements in DOM co...
Geoffrey Garen
Reported
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?
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
View All
Add attachment
proposed patch, testcase, etc.
Geoffrey Garen
Comment 1
2007-03-18 15:12:23 PDT
Created
attachment 13696
[details]
testcase for null-like arguments
Geoffrey Garen
Comment 2
2007-03-18 15:12:50 PDT
Created
attachment 13697
[details]
test case for numeric arguments
Geoffrey Garen
Comment 3
2007-03-18 15:13:48 PDT
We need to write a test for question 3. I think the rest are covered.
Ahmad Saleem
Comment 4
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!
Ryosuke Niwa
Comment 5
2022-07-19 11:36:51 PDT
Oh yeah, we improved this area some time ago.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug