[Webkit-unassigned] [Bug 43351] New: Platform network layer should be able to differentiate WebFrameLoaderClient from WebCore platform clients
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Aug 2 08:31:24 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=43351
Summary: Platform network layer should be able to differentiate
WebFrameLoaderClient from WebCore platform clients
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Platform
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: kb at inf.u-szeged.hu
In most of the ports the network backend is somewhat bounded to the platform specific API-s. For example Qt has a QWebPage::setNetworkAccessManager(QNetworkAccessManager*) API. The object that has set here is used in ResourceHandle. In the web process implementation of WebKit2, we have no platform specific FrameLoaderClient neither platform specific wrappers around WebPage, WebFrame, etc. so the backend should just do it's job without taking care of those API-s. However, it should be informed about that. My idea is to introduce a new virtual function in FrameLoaderClient (e.q. isPlatformClient).
--
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