DescriptionAdding <keygen> Content Setting (core)
Adding the KEYGEN content setting type and core functionality.
---
The purpose of the content setting is to disable <keygen> usage by default, while allowing user and enterprise settings to selectively enable <keygen>. This is early UI gating prior to the deprecation of <keygen>.
From UX discussions, we'd like to use a Page Action presented on the form rendering in order to allow the user to change the key generation settings of the page. The content setting will then determine whether the OnKeygen call actually runs the crypto to generate and store the keys.
blink-dev Thread:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/pX5NbX0Xack/kmHsyMGJZAMJ
---
BUG=514767
Committed: https://crrev.com/4d3f6bf5aeed76f36cf5982718be9e8bc6cc33ee
Cr-Commit-Position: refs/heads/master@{#359950}
Patch Set 1 #Patch Set 2 : Removing test_runner. #
Total comments: 6
Patch Set 3 : Removing keygen_rules. #
Total comments: 6
Patch Set 4 : Fixing metrics owner and test ordering. #
Total comments: 4
Patch Set 5 : Fix histograms. #Patch Set 6 : Fix typos. #
Total comments: 10
Patch Set 7 : Fixing tests. #Patch Set 8 : Rebase. #
Total comments: 4
Patch Set 9 : Moving actions.xml. #Patch Set 10 : Fixing ContentSetting Register. #Messages
Total messages: 35 (10 generated)
|