Bug 41003 - Assigning to "name" changes window.name and breaks targeted iframe navigation
Summary: Assigning to "name" changes window.name and breaks targeted iframe navigation
Status: RESOLVED DUPLICATE of bug 36459
Alias: None
Product: WebKit
Classification: Unclassified
Component: Frames (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://189.42.204.190:33445/chrome/in...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-22 11:44 PDT by Diogo Toscano
Modified: 2012-02-01 10:08 PST (History)
1 user (show)

See Also:

Attachments
3 simple html pages. (1.02 KB, application/octet-stream)
2010-06-22 11:44 PDT, Diogo Toscano 		no flags Details
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 Diogo Toscano 2010-06-22 11:44:05 PDT 
Created attachment 59399 [details]
3 simple html pages.

When a page opens an iframe, if in the iframe we call a javascript function declaring a local variable named "name", the iframe loses the original name set by the parent window.

Any submit from the parent targeting the iframe will open a blank page. The submit won't open in the iframe.
Comment 1 Diogo Toscano 2010-06-22 11:46:01 PDT 
This issues is only for Safari(version 4.0.3 - 531.9.1) and Chrome (version 5.0.375.70).

Works fine on the others browser.
Comment 2 Alexey Proskuryakov 2010-06-23 17:49:36 PDT 
Confirmed with ToT.

See also: bug 19967.
Comment 3 Diogo Toscano 2010-06-25 04:32:42 PDT 
I believe that  this bug <a href='https://bugs.webkit.org/show_bug.cgi?id=19967'>19967</a> is the same problem that i have.

The local variable "name" is making reference to window.name.

the getter and the setter is getting is accessing window.name.

And a local variable should only do reference to the local value without changing window.name.

:-)
Comment 4 Alexey Proskuryakov 2012-02-01 10:08:02 PST 

*** This bug has been marked as a duplicate of bug 36459 ***