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
Does a UA conforming to this specification expose all the attestation format interfaces (as properties on the global) even though it may never return any instances of them? Does it only expose the ones it might return instances of? Are both behaviors OK? This is not clear from the spec.
The text was updated successfully, but these errors were encountered:
Fixed small wording and markdown issues. This completes the changes to
make attestation opaque to UAs, which fixes#286, fixes#287, and fixes#289. It also fixes#239 by removing the homegrown algorithm identifiers
and specifying the algorithm explicitly in attestation data using JWK
identifiers. It also fixes#240 by encoding keys in CBOR which specifies
lengths of fields.
Does a UA conforming to this specification expose all the attestation format interfaces (as properties on the global) even though it may never return any instances of them? Does it only expose the ones it might return instances of? Are both behaviors OK? This is not clear from the spec.
The text was updated successfully, but these errors were encountered: