[Webkit-unassigned] [Bug 13062] New: Implement contentWindow for iframes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Mar 13 18:13:47 PDT 2007


http://bugs.webkit.org/show_bug.cgi?id=13062

           Summary: Implement contentWindow for iframes
           Product: WebKit
           Version: 522+ (nightly)
          Platform: PC
        OS/Version: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: netdragon at gmail.com
                CC: jhaygood at spsu.edu


There is no way to access contentWindow for iframes. That means when attempting
to do sites with dynamically loading content inside of iframes, the main page
has no way to access variables within the child frame's window, and has to
instead have all variables stored on the main window (the parent of the
frames). This causes a problem when some content inside the frames are 3rd
party (such as floating rich media content).

What should work:
document.getElementById("iframename").contentWindow.myVar

The only way to access an iframe instead:
document.getElementById("iframename").contentDocument

I attempted playing around with contentDocument.defaultView to no avail.

This issue will lead to millions in lost potential revenue for publishing sites
who use Ajax. If you want more details on why, I'd be happy to explain if you
email me, but it's probably off-topic to discuss here.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list