Bug 170413 - Need way of creating WKContextConfiguration with legacy options
Summary: Need way of creating WKContextConfiguration with legacy options
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-03 13:20 PDT by Ansh Shukla
Modified: 2017-04-03 15:23 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ansh Shukla 2017-04-03 13:20:14 PDT 
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.
Comment 1 Sam Weinig 2017-04-03 15:23:05 PDT 
(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.