Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311)

This topic came up on the WG call this week, and I think there was some skepticism about trying to optimize for FP this early, especially given that we don't yet have clear, broad vendor support for it.

We've chatted more on the Chrome side, and we're okay keeping support for "allowpaymentrequest" as an attribute on the iFrame. Our preference would be that it has the same semantics as a feature policy of {"paymentrequest": ["*"]}, which is how it's currently spec'd.

For future specs that are trying to do something similar (i.e. allow a feature within an iframe), we'll probably bring up this discussion again. 😉 

It seems like there is still a desire to upstream the attribute to HTML as @annevk and @marcoscaceres suggest. I'm not quite sure what that means, so does someone else want to handle that? 😃 

cc @adrianba 

-- 
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/browser-payment-api/issues/311#issuecomment-264554355