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

make CORS settings attributes consistent #9834

Merged

Conversation

keithamus
Copy link
Contributor

@keithamus keithamus commented Oct 5, 2023

Refs #9832

This formats the wording & HTML acround CORS - setttings attribute such that it is consistent with the format described in #9832

  • At least two implementers are interested (and none opposed):
  • Tests are written and can be reviewed and commented upon at:
  • Implementation bugs are filed:
    • Chromium: …
    • Gecko: …
    • WebKit: …
    • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
    • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
  • MDN issue is filed: …
  • The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)


/urls-and-fetching.html ( diff )

@keithamus keithamus added the editorial Changes that do not affect how the standard is understood label Oct 5, 2023
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

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

Thanks!

You also need "Keywords" -> "Keyword" in the table heading and flip the order of the first two table columns. As in, "Keyword" first, then "State".

I'm having second thoughts on requiring closing tags for tables as @domenic suggested "offline" we don't need them and I don't particularly care for them. Since you didn't add them for a bunch of elements in the table, maybe leave those changes out altogether for now?

@keithamus keithamus force-pushed the make-cors-settings-attributes-consistent branch 2 times, most recently from 97b7195 to 97f045f Compare October 5, 2023 09:07
source Show resolved Hide resolved
@keithamus keithamus force-pushed the make-cors-settings-attributes-consistent branch from 97f045f to 64ee40a Compare October 5, 2023 09:28
@annevk annevk merged commit bbc8b07 into whatwg:main Oct 5, 2023
1 check passed
@keithamus keithamus deleted the make-cors-settings-attributes-consistent branch October 5, 2023 11:26
<p>A <dfn>CORS settings attribute</dfn> is an <span>enumerated attribute</span>. The following
table lists the keywords and states for the attribute &mdash; the states given in the first cell
of the rows with keywords give the states to which those keywords map.</p>
<p>A <dfn>CORS settings attribute</dfn> The attribute is an <span>enumerated attribute</span> with
Copy link
Member

Choose a reason for hiding this comment

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

This seems like a typo? The attribute is extra.

Copy link
Member

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial Changes that do not affect how the standard is understood
Development

Successfully merging this pull request may close these issues.

3 participants