Summary: | Incorrect cross-domain errors when document.domain properly set | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Andy Maag <Andy.Maag> | ||||
Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Major | CC: | bcn, mrowe, sam | ||||
Priority: | P2 | Keywords: | InRadar, Regression | ||||
Version: | 523.x (Safari 3) | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Attachments: |
|
Description
Andy Maag
2007-11-28 12:57:09 PST
Created attachment 17578 [details]
Test case for reproducing error
We tried out the nightly build from 11/28/07 (Webkit-r28063) on Windows XP and OS X 10.4.11 and most of the issues related to this problem appear to have already been resolved. The test case attached to this ticket no longer causes any problems in Webkit-r28063. However, this issue still exists in some cases. I don't have a standalone test case at this time, however you can reproduce the issue by attempting to submit a review on a product at burpee.com. In Webkit-r28063, you'll see that uploading photos with your review at burpee.com does not work and the JavaScript console will have the usual error about cross-frame scripting from different sources. We think we narrowed down which build fixed some of the issues. Webkit nightly build 26801 seems to be the first nightly build since Safari 3.0.4 where some of the issues are resolved. [26780] seemed to be the relevant changeset. As I mentioned earlier, these changes didn't resolve all of the issues. Comment on attachment 17578 [details]
Test case for reproducing error
Obsoleting the attachment as it no longer shows the issue.
The latest nightly build as of 11/4/2007 appears to fix the issues we were having with cross-domain errors. When will it be possible to have this fix released to production? Releases are based on Apple's schedule, and we don't comment about the schedule for future releases. Since you mention that this issue is fixed in the latest nightly builds, can we go ahead and mark this bug as fixed? (In reply to comment #7) > ...Since you mention that this issue is fixed in the latest > nightly builds, can we go ahead and mark this bug as fixed? > I'm assuming nightly builds run with the same permission checking as official builds? If so, then yes, this can be marked as fixed and we can open new issues if we discover anything else. Yes, that is the case. Thanks for the bug report! |