Skip to content

Define members in the IDL (not separately) #302

@pejic

Description

@pejic

Currently the spec code defines members in a separate <dl dfn-for="Type"> block. It has been recommended that the spec rely on the references to the IDL.

For example isPayment and rpId are currently defined below the IDL.

    <xmp class="idl">
    [...]
    dictionary AuthenticationExtensionsPaymentInputs {
      boolean isPayment;

      // Only used for authentication.
      USVString rpId;
      [...]
    };
    </xmp>

    <dl dfn-type="dict-member" dfn-for="AuthenticationExtensionsPaymentInputs">
      :  <dfn>isPayment</dfn> member
      :: Indicates that the extension is active.

      :  <dfn>rpId</dfn> member
      :: The [=Relying Party=] id of the credential(s) being used. Only used at authentication time; not registration.

      [...]

    </dl>

Instead, remove the <dl> and <dfn> and reference the member.

    <xmp class="idl">
    [...]
    dictionary AuthenticationExtensionsPaymentInputs {
      boolean isPayment;

      // Only used for authentication.
      USVString rpId;
      [...]
    };
    </xmp>

    :  {{AuthenticationExtensionsPaymentInputs/isPayment}}
    :: Indicates that the extension is active.

    :  {{AuthenticationExtensionsPaymentInputs/rpId}}
    :: The [=Relying Party=] id of the credential(s) being used. Only used at authentication time; not registration.

    [...]

This issue was raised by @domfarolino in #286 (comment)_

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions