Add kid to JsonWebKey definition

[funkybob]

This is to address microsoft/TypeScript#26854

[sandersn]

@funkybob you need to commit the generated code in addition to the widl change.

[HolgerJeromin]

Thanks for jumping in.
This is not in the widl from upstream.
So the correct place would be the addTypes.json

[funkybob]

@sandersn I honestly don't know how to make the "generated code"... I ran into this problem when trying to migrate a project to TypeScript, figured I'd trying to solve it, and got this far before I ran out of time to contribute, and worked around it locally.

[sandersn]

It's npm run build and then you diff baseline and generated. If it looks right, then you run npm run baseline-accept.

[msftclas]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

❌ funkybob sign now
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[saschanaz]

Looks like this is not in the WebCrypto spec. Filing an issue there may help. (Reposting from microsoft/TypeScript#26854 (comment))

[sandersn]

Sounds like we should close this here then.

[pranjaldaffodil]

Can't believe nobody bothered to report this to W3C in 8 years! I have opened w3c/webcrypto#427 now

[pranjaldaffodil]

@sandersn what's the process once WebCrypto updates it on their side?

[saschanaz]

It will be automatically updated as the crawled spec data is served by @webref/idl

[pranjaldaffodil]

It will be automatically updated as the crawled spec data is served by @webref/idl

What about adding an interface for JWK Set? It should be relatively simple to create, but will that also require changes in WebCrypto spec?

I noticed that not just kid but there were even more missing parameters/attributes and have added them to the above mentioned issue.

[saschanaz]

Not being in the spec implies not being in browser implementations, so yes