fedcm

edit

WPT coverage of the tests of fedcm 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
Stable5968087%
Tentative714050%
Reftests000–
Crash tests000–
All6682080%

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: 6
  • NOT IMPLEMENTED: 9
  • TEST RUNNER: 1

Stable tests

TestResultSubtestsKindDescription
alternative-identifiers/fedcm-single-identifier.https.htmlPass1 / 1
fedcm-abort-silent-mediation-not-permitted.https.htmlPass1 / 1
fedcm-abort.https.htmlPass1 / 1
fedcm-accounts-endpoint-rejects-redirects.https.htmlPass1 / 1
fedcm-after-abort.https.htmlPass1 / 1
fedcm-authz/fedcm-continue-on-disallowed.https.htmlPass1 / 1
fedcm-authz/fedcm-continue-on-with-account.https.htmlPass1 / 1
fedcm-authz/fedcm-continue-on.https.htmlPass1 / 1
fedcm-authz/fedcm-disclosure-text-shown.https.htmlPass4 / 4
fedcm-authz/fedcm-params.https.htmlPass2 / 2
fedcm-authz/fedcm-resolve-side-effects.https.htmlPass1 / 1
fedcm-authz/fedcm-userinfo-after-resolve.https.htmlPass1 / 1
fedcm-authz/resolve-after-preventsilentaccess.https.htmlPass1 / 1
fedcm-auto-reauthn-without-approved-clients.https.htmlPass1 / 1
fedcm-auto-selected-flag.https.htmlFail0 / 1TEST BUGthe test assumes that the third-party cookies of the identity provider are blocked: an account whose approved_clients contains the clientId is eligible for auto reauthentication when the third-party cookies of its provider are available (https://w3c-fedid.github.io/FedCM/#eligible-for-auto-reauthentication), which they are in the runner (as in the browsers that do not block them), so two accounts are eligible and the account chooser is shown instead of the auto reauthentication
fedcm-basic.https.htmlPass1 / 1
fedcm-client-metadata-not-cached.https.htmlPass1 / 1
fedcm-context.https.htmlPass4 / 4
fedcm-cross-origin-policy.https.htmlPass1 / 1
fedcm-csp.https.htmlPass1 / 1
fedcm-delegation/evt-basic.https.htmlFail1 / 2NOT IMPLEMENTEDthe Email Verification Protocol (the email-verification-token autofill of the form fields, issued by the identity provider)
fedcm-disconnect-errors.https.htmlPass3 / 3
fedcm-disconnect-iframe.sub.https.htmlPass3 / 3
fedcm-disconnect.sub.https.htmlPass7 / 7
fedcm-domainhint-any.https.htmlPass1 / 1
fedcm-domainhint-matches-account.https.htmlPass1 / 1
fedcm-domainhint-matches-from-two-accounts.https.htmlPass1 / 1
fedcm-error-attribute/fedcm-error-attribute.https.htmlPass4 / 4
fedcm-error-basic.https.htmlPass3 / 3
fedcm-flexible-token/basic.https.htmlPass8 / 8
fedcm-flexible-token/complex.https.htmlPass6 / 6
fedcm-flexible-token/resolve-flexible-tokens.https.htmlPass6 / 6
fedcm-identity-assertion-nocors.https.htmlPass1 / 1
fedcm-iframe.https.htmlTimeout5 / 6TEST RUNNERthe runner does not serve localhost: the iframe of http://localhost:8000 is not loaded
fedcm-login-status/confirm-idp-login.https.htmlFail0 / 1TEST BUGthe login page sets the accounts cookie with document.cookie without SameSite attribute: the cookie is Lax by default (https://httpwg.org/http-extensions/draft-ietf-httpbis-rfc6265bis.html#name-the-samesite-attribute), and the accounts endpoint is fetched with the cookies of a cross-site request (SameSite=None, https://w3c-fedid.github.io/FedCM/#fetch-the-accounts, which fedcm-same-site-none.https.html checks), so the accounts are still empty and the confirm IDP login dialog is shown again
fedcm-login-status/cross-origin-status.https.htmlPass5 / 5
fedcm-login-status/idp-login-with-failed-accounts-fetch.https.htmlPass1 / 1
fedcm-login-status/logged-out.https.htmlPass2 / 2
fedcm-login-status/login-page-broken.https.htmlPass1 / 1
fedcm-loginhint.https.htmlPass3 / 3
fedcm-manifest-not-in-list.https.htmlPass1 / 1
fedcm-multi-idp/fedcm-multi-idp-abort.https.htmlPass1 / 1
fedcm-multi-idp/fedcm-multi-idp-basic.https.htmlPass2 / 2
fedcm-multi-idp/fedcm-multi-idp-context.https.htmlPass2 / 2
fedcm-multi-idp/fedcm-multi-idp-mediation-optional.https.htmlFail2 / 3TEST BUG"Mediation optional automatically succeeds when there is one returning account": the test assumes that the third-party cookies of the identity provider are blocked: an account whose approved_clients contains the clientId is eligible for auto reauthentication when the third-party cookies of its provider are available (https://w3c-fedid.github.io/FedCM/#eligible-for-auto-reauthentication), which they are in the runner (as in the browsers that do not block them), so two accounts are eligible and the account chooser is shown instead of the auto reauthentication
fedcm-multi-idp/fedcm-multi-idp-mediation-silent.https.htmlPass3 / 3
fedcm-multi-idp/fedcm-too-many-idps.https.htmlPass1 / 1
fedcm-navigation-interception/continue-on-redirect-POST.https.htmlTimeout0 / 1NOT IMPLEMENTEDthe navigation interception of FedCM (the federation-initiate-request response header) and the redirect options of IdentityProvider.resolve()
fedcm-no-domainhint-matches-account.https.htmlPass1 / 1
fedcm-no-login-url.https.htmlPass1 / 1
fedcm-nonce-is-optional.https.htmlPass1 / 1
fedcm-not-observed-by-service-worker.https.htmlPass1 / 1
fedcm-opaque-rp-origin.https.htmlPass1 / 1
fedcm-pending-call-rejected.https.htmlPass1 / 1
fedcm-pending-disconnect.https.htmlPass1 / 1
fedcm-pending-userinfo.https.htmlPass1 / 1
fedcm-register/fedcm-no-registered-idps.https.htmlFail0 / 1NOT IMPLEMENTEDthe registration of identity providers (IdentityProvider.register()): the config URL any is not a valid URL, so the request is rejected with an InvalidStateError (as the browsers reject an invalid config URL) instead of the NetworkError of an unregistered provider
fedcm-reject-invalid-responses.https.htmlPass5 / 5
fedcm-returning-account-auto-reauthn.https.htmlFail0 / 1TEST BUGthe test assumes that the third-party cookies of the identity provider are blocked: an account whose approved_clients contains the clientId is eligible for auto reauthentication when the third-party cookies of its provider are available (https://w3c-fedid.github.io/FedCM/#eligible-for-auto-reauthentication), which they are in the runner (as in the browsers that do not block them), so two accounts are eligible and the account chooser is shown instead of the auto reauthentication
fedcm-same-site-none.https.htmlPass1 / 1
fedcm-store.https.htmlPass1 / 1
fedcm-token-endpoint-rejects-redirects.https.htmlPass1 / 1
fedcm-token-returned-with-http-error.https.htmlPass1 / 1
fedcm-too-many-disconnect-calls.https.htmlPass1 / 1
fedcm-userinfo.https.htmlPass3 / 3
fedcm-well-known-validation/well-known-client-metadata-validation.https.htmlFail4 / 8TEST BUGthe identity provider is same site with the site, so its well-known file is not fetched (https://w3c-fedid.github.io/FedCM/#fetch-the-config-file, skipWellKnown): the requests that the test expects to fail because of the format of the well-known file succeed
third-party-iframe/fedcm-third-party-iframe-active-mode.https.htmlPass1 / 1
third-party-iframe/fedcm-third-party-iframe.https.htmlPass1 / 1

Tentative tests

TestResultSubtestsKindDescription
fedcm-accounts-push/fedcm-accounts-push-basic.tentative.https.htmlError0 / 1NOT IMPLEMENTEDthe tentative accounts push of FedCM (the accounts of the options of navigator.login.setStatus(), used instead of the accounts endpoint, and the prefetch of their pictures)
fedcm-accounts-push/fedcm-accounts-push-caches-pictures.tentative.https.htmlFail0 / 1NOT IMPLEMENTEDthe tentative accounts push of FedCM (the accounts of the options of navigator.login.setStatus(), used instead of the accounts endpoint, and the prefetch of their pictures)
fedcm-accounts-push/fedcm-identity-create-store-collect.tentative.sub.https.htmlError0 / 16NOT IMPLEMENTEDthe tentative lightweight FedCM (navigator.credentials.create({ identity }), the IdentityCredential constructor, the stored identity credentials and their discovery by origin and loginURL)
fedcm-accounts-push/fedcm-identity-discovery.tentative.sub.https.htmlError0 / 5NOT IMPLEMENTEDthe tentative lightweight FedCM (navigator.credentials.create({ identity }), the IdentityCredential constructor, the stored identity credentials and their discovery by origin and loginURL)
fedcm-accounts-push/store-account-list.tentative.https.htmlFail3 / 4NOT IMPLEMENTEDthe tentative accounts push of FedCM: the second argument of navigator.login.setStatus() is ignored, so an invalid account is not rejected with a TypeError
fedcm-button-and-other-account/fedcm-active-cannot-replace-active.tentative.https.htmlPass1 / 1
fedcm-button-and-other-account/fedcm-active-replaces-passive.tentative.https.htmlPass1 / 1
fedcm-button-and-other-account/fedcm-button-mode-auto-selected-flag.tentative.https.htmlFail0 / 1TEST BUGthe test assumes that the third-party cookies of the identity provider are blocked: an account whose approved_clients contains the clientId is eligible for auto reauthentication when the third-party cookies of its provider are available (https://w3c-fedid.github.io/FedCM/#eligible-for-auto-reauthentication), which they are in the runner (as in the browsers that do not block them), so two accounts are eligible and the account chooser is shown instead of the auto reauthentication
fedcm-button-and-other-account/fedcm-button-mode-basics.tentative.https.htmlPass3 / 3
fedcm-button-and-other-account/fedcm-passive-after-active.tentative.https.htmlPass1 / 1
fedcm-button-and-other-account/fedcm-passive-cannot-replace-active.tentative.https.htmlPass1 / 1
fedcm-button-and-other-account/fedcm-use-other-account-button-flow.tentative.https.htmlPass2 / 2
fedcm-button-and-other-account/fedcm-use-other-account.tentative.https.htmlPass1 / 1
fedcm-storage-access-api-autogrant.tentative.https.sub.htmlFail0 / 3NOT IMPLEMENTEDthe storage access granted to the frames of an identity provider whose account is connected to the site; and the requests of FedCM do not bypass the blocking of the third-party cookies, so the accounts endpoint gets no cookie once the test blocks them