[webkit-dev] Issue with Safari and IFrame
samyem at gmail.com
Tue Mar 24 18:39:52 PDT 2009
I will file the bug. However, I need a workaround for this. You see with
frameworks like GWT that run from within an iframe, I need to get a viable
workaround to work with the existing user base on safari. This issue does
not happen in chrome, which is partly based on webkit as well.
In GWT, all the elements are evaluated within the context of the iframe and
individual DOM element references are passed to a library like prototype.
Now with this bug, I am pretty much stuck without an alternative.
Brady Eidson wrote:
> Seems like a great reproducible example of a bug, please file it at
> On Mar 24, 2009, at 1:48 PM, samyem wrote:
>> I have a test case here:
>> When you click on the button on the iframe, it should be calling the
>> document and fading one of the divs. It works that way in all browsers
>> except for Safari (tested on 3.2.2 and 4 beta). However, if line 12 in
>> iframe.html is commented, everything seem to work in safari. Not
>> making too
>> much sense to me. Any clue what's happening here?
>> View this message in context:
>> Sent from the Webkit mailing list archive at Nabble.com.
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
View this message in context: http://www.nabble.com/Issue-with-Safari-and-IFrame-tp22689466p22693652.html
Sent from the Webkit mailing list archive at Nabble.com.
More information about the webkit-dev