WebKit2Feature

Describes a web engine feature that may be toggled at runtime.

The WebKit web engine includes a set of features which may be toggled programmatically, each one represented by a WebKitFeature that provides information about it:

• A unique “identifier”: webkit_feature_get_identifier().
• A “default value”, which indicates whether the option is enabled automatically: webkit_feature_get_default_value().
• Its “status”, which determines whether it should be considered user-settable and its development stage (see WebKitFeatureStatus for details): webkit_feature_get_status().
• A category, which may be used to group features together: webkit_feature_get_category().
• An optional short “name” which can be presented to an user: webkit_feature_get_name().
• An optional longer “detailed” description: webkit_feature_get_details().

The lists of available features can be obtained with webkit_settings_get_all_features(), webkit_settings_get_experimental_features(), and webkit_settings_get_development_features()). As a rule of thumb, applications which may want to allow users (i.e. web developers) to test WebKit features should use the list of experimental features. Additionally, applications might want to expose development features when targeting technically inclined users for early testing of in-development features (i.e. in “technology preview” or “canary” builds).

Applications must not expose the list of all features to end users because they often lack descriptions and control parts of the web engine which are either intended to be used during development of WebKit itself, or in specific scenarios to tweak how WebKit integrates with the application.