Closed Bug 379189 Opened 17 years ago Closed 14 years ago

Implement validation for the accept attribute

Categories

(Core :: DOM: Core & HTML, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: sciguyryan, Assigned: sciguyryan)

References

Details

After taking to Boris about this it seems best that I don't try to cobble together a temporary validation system for the accept attribute and this wait for bug 345624 to implement the validation framework from the WF2 specification. Once this is done I can then use this framework to validate as is specified in the WF2 specification.
Component: DOM: HTML → DOM: Core & HTML
QA Contact: ian → general
Ryan, AFAICT, there is no validation mechanism for the accept attribute. If there were one in WF2, it has been removed in HTML5 so maybe we should close this bug ?
There was one at one point but if it isn't there now then I'm not sure this bug needs to remain open. That is unless someone has an objection and wishes to get the feature re-added to the specification.

I have no issue with closing this bug as it stands so feel free to do so. If anyone has an objection to file it can always be re-opened if the specification changes again.
Ok, then let's close this bug as I see no need for a validation for the accept attribute.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
I do have one question - are there any feedback systems in the current implementation that allow a site to check if the uploaded file was matched by the accept or does it just fail to progress any further?
I would say the check has to be done server-side. HTML5 Forms do not aim to prevent server-side checks. They try to make the life of the user and page authors easier so with accept="image/*" for example, the user will know the page wants an image and the file picker will only show images.
If that is the case then I think this bug should indeed be closed. Thanks for the clarification Mounir!
You need to log in before you can comment on or make changes to this bug.