Skip to content

Rely on the IDL definitions for dictionary members. #304

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

Merged
merged 5 commits into from
Jul 16, 2025

Conversation

pejic
Copy link
Collaborator

@pejic pejic commented Jun 17, 2025

Before this change dictionaries and their members were defined in IDL blocks, then the members were redefined using <dfn> elements inside <dl>. After this change the <dfn> and <dl>'s are removed; instead the IDL definitions of the members are referenced.

Additionally, this change reuses the styles for the domintro class from the WHATWG styles. Notably, this adds "For web developers (non-normative)" as a heading to each domintro block.

See issue #302.


Preview | Diff

Before this change dictionaries and their members were defined in IDL
blocks, then the members were redefined using `<dfn>` elements inside
`<dl>`. After this change the `<dfn>` and `<dl>`'s are removed; instead
the IDL definitions of the members are referenced.

Additionally, this change reuses the styles for the domintro class from
the WHATWG styles. Notably, this adds "For web developers
(non-normative)" as a heading to each domintro block.

See issue w3c#302.
@ianbjacobs
Copy link
Collaborator

(This is not my speciality so I defer.)

@stephenmcgruer
Copy link
Collaborator

Just to check, this is not currently marked as having any reviewers - @pejic , were you looking for it to be reviewed?

@pejic
Copy link
Collaborator Author

pejic commented Jun 26, 2025

Just to check, this is not currently marked as having any reviewers - @pejic , were you looking for it to be reviewed?

There was a check failure that I was going to find the time to resolve; however, the checks do pass now: So review can begin. I will add you, Stephen, to review.

@pejic pejic requested a review from stephenmcgruer June 26, 2025 20:37
spec.bs Outdated
:: Indicates that the extension is active.

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

Choose a reason for hiding this comment

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

If this is now for web developers specifically, it should say "Only used at authentication time, not registration, and should not be set directly by web developers." or similar, here and below.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done. browserBoundPubKeyCredParams can be set on registration so the description is slightly different for that field.

pejic added a commit to pejic/secure-payment-confirmation that referenced this pull request Jul 10, 2025
Addressing stephenmcgruer's feedback on w3c#304
* Add steps for checking well-formed language tags are in
  SecurePaymentConfirmationRequest/locale.
* Adjusting the language inside domintro to the target audience, web
  developers.
pejic added a commit to pejic/secure-payment-confirmation that referenced this pull request Jul 10, 2025
Addressing stephenmcgruer's feedback on w3c#304
* Add steps for checking well-formed language tags are in
  SecurePaymentConfirmationRequest/locale.
* Adjusting the language inside domintro to the target audience, web
  developers.
Addressing stephenmcgruer's feedback on w3c#304
* Add steps for checking well-formed language tags are in
  SecurePaymentConfirmationRequest/locale.
* Adjusting the language inside domintro to the target audience, web
  developers.
Copy link
Collaborator Author

@pejic pejic left a comment

Choose a reason for hiding this comment

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

Hi @stephenmcgruer, please take another look.

spec.bs Outdated
:: Indicates that the extension is active.

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

Choose a reason for hiding this comment

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

Done. browserBoundPubKeyCredParams can be set on registration so the description is slightly different for that field.

pejic added 3 commits July 15, 2025 15:38
Other PaymentCredentialInstrument members were moved into domintro and
no longer double-defined. This occurred in a separate branch from the
introduction of the details member. So after the merge commit this fix
needs to be applied.
@pejic pejic requested a review from stephenmcgruer July 16, 2025 14:11
@stephenmcgruer stephenmcgruer merged commit da7256d into w3c:main Jul 16, 2025
3 checks passed
github-actions bot added a commit that referenced this pull request Jul 16, 2025
SHA: da7256d
Reason: push, by stephenmcgruer

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot added a commit that referenced this pull request Jul 16, 2025
SHA: da7256d
Reason: push, by stephenmcgruer

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants