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.

Sign up for GitHub

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

Jump to bottom

html forms are not checked when determining if a file is scripted #1282

Closed
xworld21 opened this issue Sep 25, 2021 · 0 comments
Closed

html forms are not checked when determining if a file is scripted #1282

xworld21 opened this issue Sep 25, 2021 · 0 comments
Assignees
@rdeltour
Labels
status: completed Work completed, can be closed type: false-negative This issue is about invalid content being incorrectly accepted
Milestone
v5.0.0-beta

Comments

@xworld21
Copy link

xworld21 commented Sep 25, 2021 •
edited
Loading

I understand that scripted document are ones containing script elements "and/or HTML forms", according to [1]. However, epubcheck seems to ignore the <form> element when checking the correct use of scripted.

On the other hand, the rest of the spec seems to use the word "scripted" only for actual scripts, not forms, so the issue is not entirely clear to me. Could it be a spec problem? The 3.3 draft is clearer about this [2].

[1] https://www.w3.org/publishing/epub3/epub-packages.html#scripted
[2] https://www.w3.org/TR/epub-33/#sec-scripted-content
@rdeltour rdeltour self-assigned this Nov 12, 2021
@rdeltour rdeltour added status: accepted Ready to be further processed type: false-negative This issue is about invalid content being incorrectly accepted labels Nov 12, 2021
@rdeltour rdeltour added this to the v5.0.0-beta-1 milestone Nov 12, 2021
@rdeltour rdeltour added status: in progress The issue is being implemented by the development team and removed status: accepted Ready to be further processed labels Nov 17, 2022
@rdeltour rdeltour added status: completed Work completed, can be closed and removed status: in progress The issue is being implemented by the development team labels Dec 1, 2022
@rdeltour rdeltour mentioned this issue Dec 2, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rdeltour rdeltour

Labels
status: completed Work completed, can be closed type: false-negative This issue is about invalid content being incorrectly accepted
Projects
None yet
Milestone
v5.0.0-beta
Development

No branches or pull requests
2 participants
@rdeltour @xworld21