Bug 170413
| Summary: | Need way of creating WKContextConfiguration with legacy options | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ansh Shukla <ansh_shukla> |
| Component: | WebKit API | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | sam |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
Ansh Shukla
Safari uses WKContext to configure its web processes. Under the covers, the default initializer we use for WKContext uses ProcessPoolConfiguration::createWithLegacyOptions() to instantiate some configuration options. We would like to change some of these options and, consequently, need support for first getting a WKContextConfiguration with these legacy options.
As a result, we want to add WKContextConfigurationCreateWithLegacyOptions() API which simply returns the ProcessPoolConfiguration created with legacy options.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Sam Weinig
(In reply to Ansh Shukla from comment #0)
> Safari uses WKContext to configure its web processes. Under the covers, the
> default initializer we use for WKContext uses
> ProcessPoolConfiguration::createWithLegacyOptions() to instantiate some
> configuration options. We would like to change some of these options and,
> consequently, need support for first getting a WKContextConfiguration with
> these legacy options.
>
> As a result, we want to add WKContextConfigurationCreateWithLegacyOptions()
> API which simply returns the ProcessPoolConfiguration created with legacy
> options.
You can probably emulate this by just creating a WKContext the way you are, casting it to a WKProcessPool, and grabbing the _WKProcessPoolConfiguration.