Bug 21787 - postMessage null origin
Summary: postMessage null origin
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Adam Barth
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-22 01:07 PDT by Adam Barth
Modified: 2008-10-23 03:00 PDT (History)
2 users (show)

See Also:

Attachments
Patch (13.36 KB, patch)
2008-10-22 03:04 PDT, Adam Barth 		sam: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Barth 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.
Comment 1 Adam Barth 2008-10-22 01:14:22 PDT 
Patch forthcoming.
Comment 2 Adam Barth 2008-10-22 03:04:53 PDT 
Created attachment 24554 [details]
Patch

Yay for merging these functions.
Comment 3 Adam Barth 2008-10-23 03:00:25 PDT 
Fixed in http://trac.webkit.org/changeset/37805