[Webkit-unassigned] [Bug 16176] New: Incorrect cross-domain errors when document.domain properly set

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Nov 28 12:57:09 PST 2007


           Summary: Incorrect cross-domain errors when document.domain
                    properly set
           Product: WebKit
           Version: 523.x (Safari 3)
          Platform: PC
        OS/Version: Windows XP
            Status: UNCONFIRMED
          Severity: Critical
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: Andy.Maag at gmail.com

Safari 3.0.4 seems to have introduced behavior that causes cross-domain error
checking to be overly strict and not obey the same origin rule as other
browsers do.

We have boiled this test case down to a simple example that works on other
browsers, worked in Safari 3.0.3, but fails on 3.0.4 (Windows and Mac).  I will
try attaching the test case to this ticket.  The workaround posed in the
testcase does not seem to work in all cases for us, so this is a critical
issue, especially because it occurs on the Mac where Safari 3.0.4 is not in

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