Bug 24795
| Summary: | Issues with evaluating DOM elements from IFrame to Parent | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Samyem Tuladhar <samyem> |
| Component: | WebCore JavaScript | Assignee: | Cameron Zwarich (cpst) <zwarich> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | Major | CC: | ap, emacemac7, zwarich |
| Priority: | P2 | Keywords: | NeedsReduction |
| Version: | 525.x (Safari 3.2) | ||
| Hardware: | PC | ||
| OS: | All | ||
| URL: | http://www.yomari.net/~samyem/tests/test.html | ||
Samyem Tuladhar
The URL attached with this bug demonstrates with the webkit build in safari having issues when DOM evaluations occur against a parent context in an iframe. All browsers, including Chrome, fades one of the DIVs when the button is clicked on the iframe except for Safari (both 3 and 4). Commenting the line that evaluates the parent.document.getElementById in IFrame makes the call properly as in other browser, but just by simply evaluating the element itself distorts further calls (in this case to the fade function) against the element.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Samyem Tuladhar
The Test case is at
http://www.yomari.net/~samyem/tests/test.html
Cameron Zwarich (cpst)
I'll try to make a reduction that doesn't depend on prototype.
Alexey Proskuryakov
See also: bug 26520.
Alexey Proskuryakov
I can no longer reproduce with recent WebKit builds (I'm on r55339).