Bug 24522 - Add test cases to check precedence of window.location and navigator versus a DOM element
Summary: Add test cases to check precedence of window.location and navigator versus a ...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Pam Greene (IRC:pamg)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-11 14:08 PDT by Pam Greene (IRC:pamg)
Modified: 2009-03-12 11:38 PDT (History)
0 users

See Also:

Attachments
Modified test + new results (2.54 KB, patch)
2009-03-11 14:10 PDT, Pam Greene (IRC:pamg) 		ap: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pam Greene (IRC:pamg) 2009-03-11 14:08:34 PDT 
Make sure window.location and window.navigator have higher lookup precedence than a DOM element with that ID.
Comment 1 Pam Greene (IRC:pamg) 2009-03-11 14:10:26 PDT 
Created attachment 28492 [details]
Modified test + new results
Comment 2 Alexey Proskuryakov 2009-03-12 01:13:33 PDT 
Comment on attachment 28492 [details]
Modified test + new results

r=me

Please mention in ChangeLog (or in the bug) whether these new tests give the same results in both IE and Firefox.
Comment 3 Pam Greene (IRC:pamg) 2009-03-12 11:38:45 PDT 
Thanks, landed in r41636.

* IE6 and IE7: match trunk WebKit

* FF (Mac 3.0.7): Different results (mostly "undefined") for nearly all of the items already tested by this test. It raises a SecurityError exception at the "Conflicting iframe" case and does not get to the new ones. When those are moved to the top of the test, it gives

Input by id (unique): undefined
Conflicting input id (navigator): single OTHER
Conflicting input id (location):

and raises a SecurityError exception on that third case.