Remove ability to create a WKView without a WKContextRef and WKPageGroupRef
Created attachment 112026 [details] Patch
Comment on attachment 112026 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=112026&action=review > Source/WebKit2/ChangeLog:4 > + Remove ability to create a WKView without a WKContextRef and WKPageGroupRef > + https://bugs.webkit.org/show_bug.cgi?id=70653 Why?
It is just to simplify things, removing the need for shared contexts.
Comment on attachment 112026 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=112026&action=review > Source/WebKit2/UIProcess/API/mac/WKView.mm:-204 > -- (id)initWithFrame:(NSRect)frame > -{ > - return [self initWithFrame:frame contextRef:toAPI(WebContext::sharedProcessContext())]; > -} This is the designated initializer of the superclass. Normally you have to override this, at least to return nil.
Committed r98159: <http://trac.webkit.org/changeset/98159>
It is just to simplify things, removing the need for shared contexts.(In reply to comment #4) > (From update of attachment 112026 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=112026&action=review > > > Source/WebKit2/UIProcess/API/mac/WKView.mm:-204 > > -- (id)initWithFrame:(NSRect)frame > > -{ > > - return [self initWithFrame:frame contextRef:toAPI(WebContext::sharedProcessContext())]; > > -} > > This is the designated initializer of the superclass. Normally you have to override this, at least to return nil. Good point. Is it more idiomatic to return nil or throw (or both)?