[Webkit-unassigned] [Bug 50898] Change the WebKit2 public API so there is no explicit WKPageNamespace object

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Dec 12 17:46:17 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=50898





--- Comment #10 from mitz at webkit.org  2010-12-12 17:46:17 PST ---
(In reply to comment #8)
> > > WebKit2/UIProcess/API/C/win/WKView.h:40
> > > +WK_EXPORT WKViewRef WKViewCreateForAssociatedPage(RECT rect, WKPageRef page, WKPageGroupRef pageGroup, HWND parentWindow);
> > 
> > I think a WKPageRef-based create API is an unnecessary convenience. This one is also awkwardly named. Is calling this different from calling WKViewCreate() passing the context of the page? If so, and three different WKViewCreate…() functions are needed, I suggest merging them into one and adding an options parameter.
> 
> The associate page create function is not a convenience, it is the only way ensure that two views have their WebProcess counterparts in the same WebProcess.  It should be used in cases like one page calling window.open().  I am not sure how we can merge these into one function, can you explain what its signature would be?

I see now why a separate WKPageRef-based API is needed.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list