Skip to content

Commit

Permalink
Fix spec-build errors (editorial) (#1461)
Browse files Browse the repository at this point in the history
* Fix spec-build errors (editorial)

we have a few loose-end editorial link-errors and unreferenced dfns, this addresses almost all of those. there's one link-error remaining, am not sure yet how to deal with it.

* yank {{evalByCredential}} experiment

* number steps such that gen'd html is correct
  • Loading branch information
equalsJeffH committed Aug 19, 2020
1 parent faa8de8 commit 96a4f10
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions index.bs
Expand Up @@ -5782,7 +5782,7 @@ Note: If PRF results are obtained during [=registration=] then the [=[RP]=] MUST
1. Decrypt the extension result and set {{AuthenticationExtensionsPRFOutputs/results}} to the PRF result(s), if any.

: Authenticator extension input / processing / output
:: This extension uses the [[FIDO-CTAP]] `hmac-secret` extension when communicating with the authenticator. It thus does not specify any direct authenticator interaction for [=[RPS]=].
:: [=prf|This extension=] uses the [[FIDO-CTAP]] `hmac-secret` extension when communicating with the authenticator. It thus does not specify any direct authenticator interaction for [=[RPS]=].

: Client extension output
:: <xmp class="idl">
Expand Down Expand Up @@ -5873,7 +5873,7 @@ Note: In order to interoperate, user agents storing large blobs on authenticator


: Authenticator extension processing
:: This extension directs the user-agent to cause the large blob to be stored on, or retrieved from, the authenticator. It thus does not specify any direct authenticator interaction for [=[RPS]=].
:: [=largeblob|This extension=] directs the user-agent to cause the large blob to be stored on, or retrieved from, the authenticator. It thus does not specify any direct authenticator interaction for [=[RPS]=].


# User Agent Automation # {#sctn-automation}
Expand Down Expand Up @@ -5907,13 +5907,14 @@ In order to advertise the availability of the [=extension commands=] defined bel

When [=validating capabilities=], the extension-specific substeps to validate `"webauthn:virtualAuthenticators"` with `value` are the following:

:: If `value` is not a [=boolean=] return a [=WebDriver Error=] with [=WebDriver error code=] [=invalid argument=].
Otherwise, let `deserialized` be set to `value`.
1. If `value` is not a [=boolean=] return a [=WebDriver Error=] with [=WebDriver error code=] [=invalid argument=].
2. Otherwise, let `deserialized` be set to `value`.

When [=matching capabilities=], the extension-specific steps to match `"webauthn:virtualAuthenticators"` with `value` are the following:

:: If `value` is [TRUE] and the [=endpoint node=] does not support any of the [=Virtual Authenticators=] commands,
the match is unsuccessful. Otherwise, the match is successful.
1. If `value` is [TRUE] and the [=endpoint node=] does not support any of the [=Virtual Authenticators=] commands,
the match is unsuccessful.
2. Otherwise, the match is successful.

## <dfn>Virtual Authenticators</dfn> ## {#sctn-automation-virtual-authenticators}

Expand Down

0 comments on commit 96a4f10

Please sign in to comment.