Bug 36677 - HTML5 form features should not be enabled if form submission is not impacted
Summary: HTML5 form features should not be enabled if form submission is not impacted
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC All
: P2 Major
Assignee: Nobody
Depends on:
Blocks: HTML5Forms
  Show dependency treegraph
Reported: 2010-03-26 14:41 PDT by Anne van Kesteren
Modified: 2010-04-10 01:55 PDT (History)
7 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Anne van Kesteren 2010-03-26 14:41:45 PDT
Currently a number of HTML5 form features are being landed but they apparently do not impact form submission. E.g. the required attribute is supported but a user can simply submit a form that is using it. This will very likely lead to interoperability issues and may even make that particular part of the feature impossible to implement later on, which would be bad.

(Was not quite sure who to cc, hope you don't mind mjs.)
Comment 1 Ian 'Hixie' Hickson 2010-03-26 14:45:00 PDT
This is actually quite a big deal — I hadn't realised for example that required="" as implemented in WebKit didn't block submission. If this is accurate, then we run the risk of people using it and relying on the way it doesn't block submission... and then we can't add the ability to block submission in future.
Comment 2 Kent Tamura 2010-03-26 19:28:47 PDT
A patch to prevent submission is under review; Bug#34930

I don't think the current status of WebKit is so harmful.  DOM API such as checkValidity() is useful without preventing submission.
Comment 3 Anne van Kesteren 2010-03-27 02:41:41 PDT
The problem is that sites may start to rely on the browser not performing validation so you can no longer implement it. However, if you think this will be fixed before that happens there is no problem as far as I can tell.
Comment 4 Kent Tamura 2010-04-10 01:55:47 PDT
The patch of Bug#34930 was committed.  This issue doesn't exist anymore.