fix: consider HTML form elements as scripted content #1419
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mattgarrish
approved these changes
Dec 2, 2022
There was a problem hiding this comment.
This is alright as it is, but I think the interpretation of "forms" in the specification is meant to be broader. Reading systems don't have to support any form elements, so it includes input, button, etc. outside of a form element. But the spec isn't very clear in its wording. I'm going to open an issue to clarify.
|
Scratch what I said above. After digging around through some old issues this is fine. I've opened w3c/epub-specs#2497 to clarify the ambiguity in the spec, though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1282