DescriptionRename feature policy classes.
Previously, we were using the term 'whitelist' to refer to what is more
correctly a feature policy declaration (a feature name and a whitelist of
origins), and overloading the term 'feature policy' to refer to the contents of
a feature policy header (a collection of declarations). This CL tries to
rationalize the terminology used for class naming in blink and in content.
This is part 1 of 5 in the effort to move the FeaturePolicy implementation
into the content layer, which will facilitate use of the framework for browser-
based policy decisions.
See the other CLs in this series:
[1/5] (This CL) (Rename classes)
[2/5] https://codereview.chromium.org/2654873004/ (Centralize content-side code)
[3/5] https://codereview.chromium.org/2655663004/ (Maintain parallel FP in browser)
[4/5] https://codereview.chromium.org/2651883008/ (Use content/ FP in blink)
[5/5] https://codereview.chromium.org/2656533004/ (Remove unused blink code.)
BUG=685195
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
Review-Url: https://codereview.chromium.org/2648423002
Cr-Commit-Position: refs/heads/master@{#447885}
Committed: https://chromium.googlesource.com/chromium/src/+/4dbcfdcb2ce26ac7f1a3effa09631053fe5a224a
Patch Set 1 #Patch Set 2 : Rename content classes to better match blink ones #Patch Set 3 : Rebase #Dependent Patchsets: Messages
Total messages: 22 (15 generated)
|