Bug 123596

Summary: Begin stubbing out the WKRemoteObjectCoder NSCoder subclass
Product: WebKit Reporter: Anders Carlsson <andersca>
Component: New BugsAssignee: Anders Carlsson <andersca>
Status: RESOLVED FIXED    
Severity: Normal CC: mitz
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch thorton: review+

Anders Carlsson
Reported 2013-10-31 16:23:25 PDT
Begin stubbing out the WKRemoteObjectCoder NSCoder subclass
Attachments
Patch (17.73 KB, patch)
2013-10-31 17:35 PDT, Anders Carlsson 		thorton: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Anders Carlsson
Comment 1 2013-10-31 17:35:52 PDT
Created attachment 215699 [details] Patch
Anders Carlsson
Comment 2 2013-10-31 17:47:17 PDT
Committed r158413: <http://trac.webkit.org/changeset/158413>
mitz
Comment 3 2013-10-31 21:26:34 PDT
Comment on attachment 215699 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=215699&action=review > Source/WebKit2/Shared/API/Cocoa/WKRemoteObjectCoder.mm:33 > +#import "WKData.h" > +#import "WKMutableDictionary.h" > +#import "WKNumber.h" > +#import "WKRetainPtr.h" > +#import "WKStringCF.h" Should we be using all these C API types in the implementation of the Cocoa API? I thought it was preferred to use the APIObject types.
Note You need to log in before you can comment on or make changes to this bug.