webauthn-public-key-easy: pin status to common algorithm#4020
Merged
Conversation
ab7e952 to
71f296d
Compare
Collaborator
Author
|
In the WebDX chat, @captainbrosset asks:
The answer is that we're excluding two keys:
The full list of keys (from a tag in BCD) is in the expanded diff in the |
captainbrosset
approved these changes
May 19, 2026
captainbrosset
left a comment
Contributor
There was a problem hiding this comment.
Approved, keeping in mind our conversation in chat, just now, about the fact that features like this which only list a few keys, while other keys are tagged in BCD, are a little harder to work with.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR resolves the status problem described in #3995 by pinning to the commonly-supported algorithms. See the issue for a fuller description of this approach.
This PR is blocked until the data changes proposed in #3995 is accepted. It may change and I'll leave it in draft until there's a BCD release with such data.It's possible in the future that we might break this feature up, minting for the algorithms themselves. Since this is a long-standing API with apparently little developer interest in the other algorithms, I don't think this is necessary today.
Related issues
webauthn-public-key-easyto regress to limited availability #3995getPublicKey(): add per-algorithm subfeatures mdn/browser-compat-data#29637