You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2024-05-15 WG call: Agreed we should change PublicKeyCredentialRpEntity.id to USVString. Strictly speaking this is a breaking change (changing a type bound in input (contravariant) position to be more restrictive), but in practice this shouldn't be able to break any applications since then those credentials wouldn't have worked in get() anyway.
@jschanck Seeing as Firefox is the browser that makes the most actual use of WebIDL - would changing PublicKeyCredentialRpEntity.id to USVString be a problem for Firefox?
Both
PublicKeyCredentialRpEntity.id
andPublicKeyCredentialRequestOptions.rpId
represent the same thing (i.e., RP ID); however the former is modeled as aDOMString
while the latter is modeled as aUSVString
. These should be the same type. SpecificallyPublicKeyCredentialRequestOptions.rpId
should be aDOMString
as well orPublicKeyCredentialRpEntity.id
should be aUSVString
. Should be noted thatPublicKeyCredentialRequestOptionsJSON.rpId
is already aDOMString
.The text was updated successfully, but these errors were encountered: