Now a runtime feature entry in runtime_enabled_features.json5 generates a
base::Feature instance with the same name by default.  You can disable this
behavior by specifying `base_feature: "none"`.

Existing entries in runtime_enabled_features.json5 which didn't have `
base_feature` now have `base_feature: "none"`.  In many cases you should
remove the field when you ship the feature, in order to have a kill switch.

-- 
TAMURA Kent
Software Engineer, Google

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqGqKgus%2BM8kp8L%3D8ngBm%2BbJuuS533sr3KrLKZBh7_UdSQ%40mail.gmail.com.

Reply via email to