Re: [w3c/payment-request] Integration with Feature Policy (#600)

Re what's the status on the Chrome side?

- [Feature-Policy HTTP Header Field](https://wicg.github.io/feature-policy/#feature-policy-http-header-field)
    + Note: there was a discussion about change "Feature-Policy" to "Allow" at one point but AFAIK, there weren't any action upon that. 
- [iframe allow attribute ](https://wicg.github.io/feature-policy/#iframe-allow-attribute)
- [JS introspection](https://wicg.github.io/feature-policy/#the-policy-object):
    + allowsFeature(feature, optional url);
    + allowedFeatures();
    + getAllowlistForFeature(DOMString feature);
    + Note: these JS APIs are currently in origin trial. We have them implemented but I don't think they are fully shipped yet. @clelland would know more
- In terms of features, we have a bunch supported:
Permission based like "camera", "geolocation", "microphone", "midi", "speaker", etc
Other things like: "fullscreen", "sync-xhr", "vr", etc
Meanwhile, we have experimental features such as "payment", "picture-in-picture", "usb", etc

Hope that helps. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/600#issuecomment-421393998