secure-payment-confirmation

edit

WPT coverage of the tests of secure-payment-confirmation at the revision c8fa86fb13d4. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features), the reftests and the crash tests are listed separately from the stable tests.

GroupPassingTestsDisabledPass rate
Stable1520075%
Tentative000–
Reftests000–
Crash tests000–
All1520075%

Failure reasons

The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.

  • TEST BUG: 5

Stable tests

TestResultSubtestsKindDescription
authentication-accepted-bbk-created.https.htmlPass3 / 3
authentication-accepted-bbk-per-passkey.https.htmlPass1 / 1
authentication-accepted-bbk-reused.https.htmlPass3 / 3
authentication-accepted.https.htmlPass2 / 2
authentication-auth-another-way.https.htmlPass2 / 2
authentication-cannot-bypass-spc.https.htmlFail0 / 1TEST BUGthe test gives total: PAYMENT_DETAILS['total'], a PaymentItem ({ label, amount }), to the payment extension, whose total is a PaymentCurrencyAmount (https://w3c.github.io/secure-payment-confirmation/#dictdef-authenticationextensionspaymentinputs): the conversion of the options throws a TypeError (the required member currency is missing) before the extension rejects the authentication with the expected NotAllowedError
authentication-cross-origin.sub.https.htmlPass1 / 1
authentication-icon-data-url.https.htmlPass1 / 1
authentication-in-iframe.sub.https.htmlPass2 / 2
authentication-invalid-icon.https.htmlPass2 / 2
authentication-invalid-payment-entity-logo.https.htmlPass1 / 1
authentication-optout.https.htmlPass1 / 1
authentication-rejected.https.htmlPass2 / 2
authentication-requires-user-activation.https.htmlPass1 / 1
constructor-validate-payment-method-data.https.htmlFail20 / 22TEST BUG"Large credentialIds value" and "Large challenge value" expect a TypeError for 1 MiB buffers: the steps to validate payment method data (https://w3c.github.io/secure-payment-confirmation/#sctn-steps-to-validate-payment-method-data) have no size limit (Chromium limits the JSON serialization of the data of a payment method to 1 MiB)
constructor.https.htmlPass10 / 10
enrollment-bbk-per-passkey.https.htmlPass1 / 1
enrollment-bbk.https.htmlError3 / 3TEST BUGthe subtests do not return (nor await) the promise of testBrowserBoundKeyOnPasskeyEnrollment(): they pass at once, the three registrations run concurrently, and the second and third ones are rejected with a NotAllowedError (a request for a public key credential is already pending, as in Chromium) that nothing handles, so the harness reports an error
enrollment-in-iframe.sub.https.htmlFail2 / 3TEST BUG"SPC enrollment in cross-origin iframe without payment permission": a cross-origin iframe without allow="payment" may use neither publickey-credentials-create nor payment (the alternative create permissions policy of public-key, https://w3c.github.io/secure-payment-confirmation/#sctn-permissions-policy), so create() rejects with a NotAllowedError (https://w3c.github.io/webappsec-credential-management/#algorithm-create, step 9.3: "If document is not allowed to use permission, return a promise rejected with a NotAllowedError"); the test expects the NotSupportedError of Chromium
enrollment.https.htmlFail5 / 9TEST BUGthe registration processing of the payment extension throws a TypeError when authenticatorAttachment is not platform, residentKey is not required or preferred, or userVerification is not required (https://w3c.github.io/secure-payment-confirmation/#client-extension-processing-registration: "then throw a TypeError"); the test expects a NotSupportedError