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

Disallow interactive content in <summary>. #9372

Closed

Conversation

dbaron
Copy link
Member

@dbaron dbaron commented Jun 1, 2023

This changes the content model for <summary> to have the same restriction on interactive content that is present for the content model of <button>. This affects conformance for documents but not for user agents.

Fixes #2272.

The rationale for this change is probably best described in #2272 (comment) by @scottaohara.

It looks to me like the bulk of the pull request template is not relevant here, since this change (while a normative change) affects only document conformance and not user agent conformance, and the template seems to focus on changes to user agent conformance. (It's possible we may also want to make some changes to user-agent conformance related to the handling of documents that this change would make nonconforming, but I think this change is probably the least controversial piece.) Let me know if you think I should fill out parts or all of the template, though.


/form-elements.html ( diff )
/interactive-elements.html ( diff )

This changes the content model for <summary> to have the same restriction on interactive content that is present for the content model of <button>.  This affects conformance for documents but not for user agents.

Fixes whatwg#2272.
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.

This looks fine to me.

Edit: I have some concerns: #2272 (comment).

Optional nit: align the wording with the <a> element (use "or" instead of "and no") both here and for <button> or vice versa.

@sideshowbarker should probably give this a once over as well, as Chief Validator^WChecker.

@annevk annevk added the do not merge yet Pull request must not be merged per rationale in comment label Jun 2, 2023
@sideshowbarker
Copy link
Contributor

I will not willingly implement this in the HTML checker, because I assess that on balance this restriction that the patch in this PR adds to the spec will end up wasting more time of HTML developer-authors than it helps others — or end up just being widely ignored.

Longer comment at #2272 (comment)

@dbaron
Copy link
Member Author

dbaron commented Jun 5, 2023

Based on the discussion in #2272, sounds like I should retract this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do not merge yet Pull request must not be merged per rationale in comment document conformance
Development

Successfully merging this pull request may close these issues.

Disallow interactive content in <summary>
3 participants