Feature policy should only parse names for features available in the browser |
||
Issue descriptionThe logic around which feature names can be parsed needs to be cleaned up; some features are actually behind runtime flags, but the feature names are always accepted. This will matter once we ship the `policy` interface, as the names will be exposed in `document.policy.allowedFeatures()`. In general, adding a feature to the default feature list should be contingent on that feature being available in the renderer, and should check the same runtime flags as the rest of the code for that feature.
,
Jul 25
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Jul 12