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

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


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


netdragon at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #13622|0                           |1
        is obsolete|                            |




------- Comment #3 from netdragon at gmail.com  2007-03-13 18:41 PDT -------
Created an attachment (id=13624)
 --> (http://bugs.webkit.org/attachment.cgi?id=13624&action=view)
Here is the testcase. It will work on every major browser but Safari

Previous testcase had a bug. Note that because the iframe is on the same
domain, there's no security restrictions. Some publishers utilize that
capability for dynamic load functionality when loading 3rd party content
through 3rd party scripts. The difficulty comes in when the iframes need to
share variables with the main page.

An example case of when this is needed: A publisher, we'll call MajorPublisherA
requested we support their implementation of Ajax ad serving. Their method
works by refreshing the src of the serving iframe (iframe A). MajorPublisherA
wants us, the rich media vendor, to support all major browsers. As a standard
practice, expandable advertisements break out of the ad serving iframe and may
create their own container on the main page, hovering over the serving frame,
so they can change size on user interaction. However, when the src of the
serving frame changes, the next ad will show up, but a remnant of the previous
ad will still be there. In a situation like this, we have a "hook" variable on
the window of the serving frame, and when we detect that we cannot access that
"hook" variable anymore, we know our ad's code has been rotated out, and clean
up our expandable advertisement. However, on Safari, as it stands right now,
without the contentWindow, we can't detect that the initial serving iframe's
src has been changed, and can't therefore clean up the advertisement. I believe
I've found a solution so that Safari users will get the same user experience on
MajorPublisherA, but it required a massive workaround for something that should
be simple, since it's supported on all other browsers.

Another thing all other browsers support is that you can compare window
elements inside iframes to the contentWindow of another element to see if they
match, even with domain security restrictions. You can't do anything else, but
you can compare the two variables. Please make sure when this is implemented,
it's implemented in a way that allows the capability of comparing contentWindow
and window elements across domains.


-- 
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