Hi WebKit! I'm sending this according to the policy to discuss new feature proposals on webkit-dev <https://trac.webkit.org/wiki/AddingFeatures>. We, the Google Chrome team, are exploring the possibility of shipping the W3C Secure Payment Confirmation API <https://www.w3.org/TR/secure-payment-confirmation/> in Chrome on iOS and would like to know if proposing patches in WebKit for an off-by-default feature which can be enabled at runtime by Chrome is an option we should be considering?
We had assumed our only viable option was to attempt to implement it via injected JavaScript (as we had previously implemented PaymentRequest <https://www.w3.org/TR/payment-request/>), but this may not be technically possible without changes to the specification and has obvious downsides. Based on Apple's comments about the openness of the WebKit project to third-party prioritization of features for third-party browsers [1], I figured I should at least ask to see if our assumption was out-of-date? Discussion in the WebKit standards position <https://github.com/WebKit/standards-positions/issues/30#issuecomment-1178361664> for this feature does not seem to have concluded, but we are happy to continue to engage on the details there. We'd be thrilled to collaborate with the WebKit community on this if there is interest. Thank you! Rick [1] https://assets.publishing.service.gov.uk/media/66d6c524c52d5fb4c82ddd65/2024-08-01_Apple_Response_to_Working_Papers_1_to_5_-_TO_BE_PUBLISHED.pdf p81
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
