Bug 22588

Summary: securityOrigin() should move from Document and WorkerContext into ScriptExecutionContext
Product: WebKit Reporter: David Levin <levin>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: levin
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
patch for bug. ap: review+

David Levin
Reported 2008-12-01 22:11:02 PST
Code like XMLHttpRequest should work on either the Document or WorkerContext. Moving SecurityOrigin into ScriptExecutionContext helps this goal.
Attachments
patch for bug. (15.46 KB, patch)
2008-12-01 22:54 PST, David Levin 		ap: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
David Levin
Comment 1 2008-12-01 22:54:25 PST
Created attachment 25668 [details] patch for bug.
Alexey Proskuryakov
Comment 2 2008-12-02 00:20:16 PST
Comment on attachment 25668 [details] patch for bug. r=me It is quite sad that you have to hack around the difference between ScriptExecutionContext::setSecurityOrigin and Document::setSecurityOrigin. I think that the initDNSPrefetch() call in setSecurityOrigin() is misplaced - there are lots of things that depend on protocol in loader, but we don't eagerly initialize them all in setSecurityOrigin(), or track in Document at all.
Alexey Proskuryakov
Comment 3 2008-12-02 00:49:31 PST
Committed revision 38900.
Note You need to log in before you can comment on or make changes to this bug.