Summary: | [Chromium] Add WebSecurityOrigin::createFromString factory | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Jeremy Orlow <jorlow> | ||||||
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | ||||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | Other | ||||||||
OS: | OS X 10.5 | ||||||||
Attachments: |
|
Description
Jeremy Orlow
2010-02-01 18:17:09 PST
Created attachment 47894 [details]
Patch
Comment on attachment 47894 [details] Patch > Index: WebKit/chromium/public/WebSecurityOrigin.h > WEBKIT_API static WebSecurityOrigin* createFromDatabaseIdentifier(const WebString& databaseIdentifier); > + WEBKIT_API static WebSecurityOrigin* createFromString(const WebString& origin); There's no reason for either of these to return pointers. WebSecurityOrigin is already like a smart pointer class. Just return by value. Created attachment 47908 [details]
Patch
Comment on attachment 47908 [details] Patch > Index: WebKit/chromium/public/WebSecurityOrigin.h > + WEBKIT_API static WebSecurityOrigin createFromString(const WebString& origin); nit: nix the origin parameter name. otherwise, r=me Committed r54214: <http://trac.webkit.org/changeset/54214> |