Bug 14106
| Summary: | ResourceHandle::loadResourceSynchronously lacks Frame pointer | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Darin Fisher (:fishd, Google) <fishd> |
| Component: | Platform | Assignee: | Darin Fisher (:fishd, Google) <fishd> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Minor | ||
| Priority: | P3 | ||
| Version: | 523.x (Safari 3) | ||
| Hardware: | All | ||
| OS: | All | ||
Darin Fisher (:fishd, Google)
ResourceHandle::loadResourceSynchronously lacks Frame pointer
When implementing ResourceHandle it is often useful to know the context of the guy requesting the resource. In the typical case of asychronous resource requests, a Frame pointer provides this context. However, for synchronous requests, there is no such context.
I propose that a Frame pointer be added to ResourceHandle::loadResourceSynchronously for consistency with ResourceHandle::create.
See the post to webkit-dev for more details on this issue.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Darin Fisher (:fishd, Google)
from discussions off-line it appears that sufficient context can be associated with a ResourceRequest from the FrameLoaderClient::dispatchWillSendRequest callback.
therefore, closing as WONTFIX