Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Revision history section #2224

Merged
merged 14 commits into from
Jan 15, 2025
27 changes: 27 additions & 0 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -9875,6 +9875,33 @@ Harry Halpin
for their contributions as our W3C Team Contacts.


# Revision History # {#revision-history}

This section is <i>non-normative</i>.
simoneonofri marked this conversation as resolved.
Show resolved Hide resolved

This section contains the substantive changes that have been made to this specification over time.

## Changes since Web Authentication Level 2 [[webauthn-2-20210408]]

- Two authenticatorData flags assigned:
- [[#sctn-credential-backup]]
- [[#sctn-automation-set-credential-properties]]
- [[#sctn-getClientCapabilities]]
- Conditional mediation for get: [[#sctn-getAssertion]]
- Conditional mediation for create: [[#sctn-createCredential]]
- Added topOrigin: [[#dictionary-client-data]]
- Create operations in an iframe: [[#sctn-createCredential]]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reckon this should also reference section §5.10. Using Web Authentication within iframe elements; see also #2229

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would be covered by meta-PR #2230.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Section 5.10. Using Web Authentication within iframe elements existed as-is in Level 2, so it's not a change. Therefore I don't think it should be added to this list.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As is right now, yes, but as noted in issue #2229 this section needs to be updated to reflect that create() is now also allowed in cross-origin iframes (and requires the respective feature policy).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR #2231 would make the aforementioned update.

- Extension: [[#prf-extension]]
- [[#sctn-compound-attestation]]
- Updated timeout guidance: [[#sctn-timeout-recommended-range]]
- New JSON (de)serialization methods:
- <a href="#dom-publickeycredential-tojson">toJSON() method (in 5.1. PublicKeyCredential Interface)</a>
- [[#sctn-parseCreationOptionsFromJSON]]
- [[#sctn-parseRequestOptionsFromJSON]]
- [[#sctn-related-origins]]
- [[#enum-hints]]
- [[#sctn-signal-methods]]

<pre class=biblio>
{

Expand Down