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:
Its “status”, which determines whether it should be considered
user-settable and its development stage (see enum@FeatureStatus
for details): webkit.feature.Feature.getStatus.
The lists of available features can be obtained with
webkit.settings.Settings.getAllFeatures, webkit.settings.Settings.getExperimentalFeatures,
and webkit.settings.Settings.getDevelopmentFeatures). 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.
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:
The lists of available features can be obtained with webkit.settings.Settings.getAllFeatures, webkit.settings.Settings.getExperimentalFeatures, and webkit.settings.Settings.getDevelopmentFeatures). 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.