Bug 21787

Summary: postMessage null origin
Product: WebKit Reporter: Adam Barth <abarth>
Component: DOMAssignee: Adam Barth <abarth>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, sam
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch sam: review+

Adam Barth
Reported 2008-10-22 01:07:31 PDT
Ian updated the HTML 5 spec to use "null" instead of the empty string when the browser can't serialize the current origin. This means we can get rid of SecurityOrigin::toHTTPOrigin() and just use SecurityOrigin::toString() for both postMessage and XMLHttpRequest.
Attachments
Patch (13.36 KB, patch)
2008-10-22 03:04 PDT, Adam Barth 		sam: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Adam Barth
Comment 1 2008-10-22 01:14:22 PDT
Patch forthcoming.
Adam Barth
Comment 2 2008-10-22 03:04:53 PDT
Created attachment 24554 [details] Patch Yay for merging these functions.
Adam Barth
Comment 3 2008-10-23 03:00:25 PDT
Fixed in http://trac.webkit.org/changeset/37805
Note You need to log in before you can comment on or make changes to this bug.