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

<input type="file"> needs name= #845

Closed
jidanni opened this issue Oct 26, 2019 · 2 comments
Closed

<input type="file"> needs name= #845

jidanni opened this issue Oct 26, 2019 · 2 comments

Comments

@jidanni
Copy link
Contributor

jidanni commented Oct 26, 2019

REC-html401-19991224 says:

A successful control must be defined within a FORM element and must have a control name.

Alas, tidy 5.6 allowed me to forget that I needed a name= in

<input type="file" multiple>

causing it not to append the selected files in the browser. So at
least for type="file", do catch it when people forget a name=.

@geoffmcl
Copy link
Contributor

@jidanni thank you for the issue...

Although the spec you gave, REC-html401-19991224 is marked This version is outdated!, the follow on spec html401 say the same thing about Successful Controls...

And given that Tidy, in general, aims to help the user produce valid html, BUT maybe this is too big of a stretch, to ask libtidy to check for Successful Controls, within a FORM...

In constructing both a legacy 4.01 document, and a html5 document, for testing, both the legacy W3C validator, and nu validator do not appear to have such a validation check... for a missing name attribute... both docs pass...

As they do with current tidy 5.7.28...

The question is - should tidy do more in this case?

So this seems to need much more discussion... thanks...

@geoffmcl
Copy link
Contributor

2020/10/11
@jidanni no further feedback, no clear feature emerging... so closing this...

Please feel free to reopen, with comments, or open a new issue... thanks...

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

No branches or pull requests

2 participants