custom-schemes.md: point 7 should discuss how a browser api could avoid or mitigate this problem about digital-credentials HOT 4 OPEN

custom-schemes.md doesn't have numbered points. I can't be sure which heading or paragraph you're aiming at. My best guess is I. Concerns with custom schemes for identity presentment -> D. User experience concerns -> 4. Friction and app switching. Confirmation will help someone other than the OP to contribute to this issue's resolution.

from digital-credentials.

custom-schemes.md doesn't have numbered points.

Indeed, though it did when I filed this.

I was referring to How can users be assured that they have control over where their personal information is shared?

from digital-credentials.

I was referring to How can users be assured that they have control over where their personal information is shared?

Note that that links right back to this issue, with a fragment identifier that isn't on this page. This correctly links to that section (and will at least get you to the right page, if that heading changes such that the frag-id is no longer correct).

from digital-credentials.

Assigning to @RByers... Rick, do you want to bother explaining this, or just close this out given that the spec/API doesn't deal with schemes?

from digital-credentials.