Skip to content

Add a section on "Risky changes" to the working mode #253

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

domenic
Copy link
Member

@domenic domenic commented May 23, 2025

This attempts to capture the best practice discussed in whatwg/html#11102 (comment).

Review appreciated from @zcorpan @mfreed7 @annevk.

My intent here is to capture this in a useful place, while making it less "binding" than the rest of the working mode.

This attempts to capture the best practice discussed in whatwg/html#11102 (comment).
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!


EXAMPLE: [Escape "<" and ">" when serializing attribute values](https://github.com/whatwg/html/pull/6362) was merged once it became clear that all implementations were moving toward shipping, even before the change had reached any implementation's stable channel.

* If multiple implementers are supportive of the change, but only a single implementation is taking the lead by shipping it, then it's best to wait until there's a deployed implementation that's seen significant user testing before merging into the standard.
Copy link

Choose a reason for hiding this comment

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

Perhaps s/there's a deployed/there's at least one deployed ?

Copy link

@mfreed7 mfreed7 left a comment

Choose a reason for hiding this comment

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

LGTM! Good idea to document this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants