On Tue, Oct 14, 2025 at 1:31 AM Mike Taylor <[email protected]> wrote:
> Could you clarify which milestones you're requesting? I see M143 as the > start, but no ending milestone. > > Non-blocking question: I note that the WPTs for > navigator.credentials.create() are all failing (except one) - is that > expected? > Because the content feature flag <https://source.chromium.org/chromium/chromium/src/+/main:content/public/common/content_features.cc;l=464-465;drc=82ecd28db0680663b366160401c9d5610b0b39c9> controlling the feature is currently disabled. (and can only be overridden from the chrome://flags_ It will be enabled as part of the CL that starts the OT. On 10/13/25 1:08 p.m., Chromestatus wrote: > > *Contact emails* > [email protected], [email protected], [email protected] > > *Explainer* > https://github.com/w3c-fedid/digital-credentials/blob/main/explainer.md > > *Specification* > https://w3c-fedid.github.io/digital-credentials > > *Summary* > This Web Platform feature enables issuing websites (e.g., a university, > government agency, or bank) to securely initiate the provisioning > (issuance) process of digital credentials directly into a user's mobile > wallet application. On Android, this capability leverages the Android > IdentityCredential CredMan system (Credential Manager). On Desktop, it > leverages cross-device approaches using the CTAP protocol similar to > Digital Credentials presentation. > > *Blink component* > Blink>Identity>DigitalCredentials > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EIdentity%3EDigitalCredentials%22> > > *Web Feature ID* > Missing feature > > *TAG review* > https://github.com/w3ctag/design-reviews/issues/1119 > > *TAG review status* > Pending > > *Origin Trial documentation link* > https://w3c-fedid.github.io/digital-credentials > > *Risks* > > > *Interoperability and Compatibility* > There are multiple standards efforts involved here. We have been working > with WebKit and Mozilla in the WICG on defining this specific API. But the > greater interoperability risk will come from the data that is sent and > returned via this API. Details of that are driven outside the web browser > community in the OpenID Foundation. > > *Gecko*: Negative ( > https://github.com/mozilla/standards-positions/issues/1003) > > *WebKit*: Support ( > https://github.com/WebKit/standards-positions/issues/332) Presentation > support is shipped, but timeline for adding issuance support yet. > > *Web developers*: No signals > > *Other signals*: > > *Activation* > The primary activation concern is enabling existing deployments using > technology like OpenID4VCI to be able to also support this API. As such we > have left the request protocol unspecified at this layer, to be specified > along with existing request protocols to maximize activation opportunity. > > *WebView application risks* > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > None > > > *Goals for experimentation* > > > *Ongoing technical constraints* > None > > *Debuggability* > None necessary - just new JS API. For testing we plan to add a developer > option to provide a fake wallet, but this effort is still ongoing. > > *Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, ChromeOS, Android, and Android WebView)?* > No > > *Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* > Yes > > https://wpt.fyi/results/digital-credentials?label=experimental&label=master&aligned > > *Flag name on about://flags* > web-identity-digital-credentials-creation > > *Finch feature name* > WebIdentityDigitalCredentialsCreation > > *Requires code in //chrome?* > True > > *Tracking bug* > https://crbug.com/378330032 > > *Launch bug* > https://launch.corp.google.com/launch/4418038 > > *Estimated milestones* > Origin trial desktop first 143 > DevTrial on desktop 133 > Origin trial Android first 143 > DevTrial on Android 133 > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/5099333963874304?gate=5124632629870592 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com>. > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68ed3208.050a0220.30571e.0360.GAE%40google.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68ed3208.050a0220.30571e.0360.GAE%40google.com?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOZU3iHjjopRFqeMCA%2BsOQqs1N%3Dbz5wFr9QzW90kjgtkcEQdCw%40mail.gmail.com.
