[Webkit-unassigned] [Bug 80713] Add new methods to FrameLoaderClient so different WebKit ports can customize the ResourceRequest when it is created.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Mar 13 09:18:43 PDT 2012


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





--- Comment #41 from jochen at chromium.org  2012-03-13 09:18:42 PST ---
(In reply to comment #40)
> (In reply to comment #39)
> > I'm not sure what you mean by this. The various willSendRequest methods are part of WebKit API.
> 
> I mean if the new methods I suggested is approved, then willSendRequest() is redundant and should be changed to use a const ResourceRequest, which means it is just a notification callback, not for ResourceRequest customization anymore.

The new methods are not sufficient for the chromium port.

Anyway, we need to cache the target type (or equivalently the cached resource types) already now in a few locations. I don't see that as a problem.

-- 
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