New issue
Advanced search Search tips

Issue 899366 link

Starred by 1 user
Status: Fixed
Owner:
cha...@chromium.org
Closed: Dec 3
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature



Sign in to add a comment

Integrate Feature Policy JavaScript API and reporting with flag #enable-experimental-productivity-features

Project Member Reported by cha...@chromium.org, Oct 26 
To make it easier for developers to try out all the Feature Policy bits, the JS API and reporting should also be turned on when using the chrome://flag #enable-experimental-productivity-features.

Currently, those two features are behind a Blink runtime flag, but not any chrome://flag. The only chrome://flag to turn them is the hammer of #enable-experimental-web-platform-features.
Project Member

Comment 1 by bugdroid1@chromium.org, Nov 7 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ee221c1e36d1878542e6593a2ce4b32f244c910c

commit ee221c1e36d1878542e6593a2ce4b32f244c910c
Author: Jason Chase <chasej@chromium.org>
Date: Wed Nov 07 14:21:45 2018

Change the Productivity flag to turn on all Feature Policy runtime flags

The ExperimentalProductivityFeatures flag, with a corresponding chrome
flag, was intended as an easy way for developers to turn on the Feature
Policy bits. The Feature Policy reporting functionality and JS API have
separate runtime flags.

This CL configures an implied_by relationship, so that reporting and the
JS API can be turned on together with other Feature Policy functionality.

Bug:  899366 
Change-Id: I2ff6ac9ed48902e7d1383ace94828f9e5154a27e
Reviewed-on: https://chromium-review.googlesource.com/c/1303038
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Commit-Queue: Jason Chase <chasej@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606039}
[modify] https://crrev.com/ee221c1e36d1878542e6593a2ce4b32f244c910c/third_party/blink/renderer/platform/runtime_enabled_features.json5

Comment 2 by cha...@chromium.org, Dec 3

Status: Fixed (was: Started)
►

Sign in to add a comment