ASSIGNED 31835
The URL "file://" should not cause m_noAccess to be set on SecurityOrigin. 
https://bugs.webkit.org/show_bug.cgi?id=31835
Summary The URL "file://" should not cause m_noAccess to be set on SecurityOrigin.
Adam Barth
Reported 2009-11-24 08:18:56 PST
In http://trac.webkit.org/changeset/51338, we landed a temporary fix for Bug 31833. The right fix is to use WebSecurityOrigin to represent SecurityOrigin objects instead of using strings.
Attachments
Add attachment proposed patch, testcase, etc.
Jeremy Orlow
Comment 1 2009-11-30 16:04:13 PST
I am going to switch the chromium api over to using WebSecurityOrigin, but that's not the actual issue. The actual issue is that we've found a corner case where createFromString(securityOrigin.toString()) != securityOrigin. That's what should be fixed.
Adam Barth
Comment 2 2009-11-30 16:09:12 PST
Jeremy and I chatted on IRC. createFromString(securityOrigin.toString()) can't entirely round-trip (e.g. document.domain, @sandbox), but we think it makes sense to round-trip in this case.
Note You need to log in before you can comment on or make changes to this bug.