Bug 230911
| Summary: | Add WKProcessPool public API for warmup process | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dan <dsaunders45459> |
| Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | achristensen, cdumez, dvpdiner2, ggaren, kevin_neal, kkinnunen, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Dan
In our use case we know that the user is about to load web content, but we don't know the exact URL until after some delay. It would improve perceived performance if we could start initializing WebKit including content and networking process, before knowing a URL while our application is idling. -[WKProcessPool _warmInitialProcess] is a preloading API that allows for a similar scenario, but it is private any only warms up the web content process. -[WKWebView loadHTMLString:@"<html><body></body></html" baseUrl:nil] may be a workaround to warm up the processes, but it would be more reliable if we could support this scenario with an official API. Also, if we already have one WKWebView in use, but another user action could result in a new WKWebView on different domain we could call the preload API to signal to WKWebView that it should warmup another web content process to be used on the separate domain. We primarily want to use this preloading API on Mac.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Kevin Neal
Thank you for filing. The appropriate engineers have been notified.
Radar WebKit Bug Importer
<rdar://problem/83769109>