Make content::FeaturePolicy implement WebFeaturePolicy, and use it in blink code

third_party/WebKit/Source/modules/payments/PaymentTestHelper.cpp

Index: third_party/WebKit/Source/modules/payments/PaymentTestHelper.cpp
diff --git a/third_party/WebKit/Source/modules/payments/PaymentTestHelper.cpp b/third_party/WebKit/Source/modules/payments/PaymentTestHelper.cpp
index d4e326b88afb2b7e3883cc540c1dd7b8b77e1bda..cda610edf0be8f25a8797f9f90b06f2c92aff579 100644
--- a/third_party/WebKit/Source/modules/payments/PaymentTestHelper.cpp
+++ b/third_party/WebKit/Source/modules/payments/PaymentTestHelper.cpp
@@ -169,7 +169,7 @@ payments::mojom::blink::PaymentResponsePtr buildPaymentResponseForTest() {
 }
 
 void makePaymentRequestOriginSecure(Document& document) {
-  document.setSecurityOrigin(
+  document.updateSecurityOrigin(

[raymes, 2017/02/13 04:45:22]

Are there other places that call setSecurityOrigin that should call
updateSecurityOrigin? Should setSecurityOrigin be private now? (These are
genuine questions since I don't know this code at all really :)

[iclelland, 2017/02/23 20:04:12]

That's actually a really good point -- Most of the calls to setSecurityOrigin
seem to be in initialization methods, and those, I presume, shouldn't really be
touched. Maybe the best solution here is to have setSecurityOrigin update the
policy if necessary.

(Done)

       SecurityOrigin::create(KURL(KURL(), "https://www.example.com/")));
 }