Bug 28145 - novalidate/formnovalidate support
: novalidate/formnovalidate support
Status: RESOLVED FIXED
: WebKit
Forms
: 528+ (Nightly build)
: All All
: P2 Enhancement
Assigned To:
: http://www.whatwg.org/specs/web-apps/...
:
:
: 19264 28649 28988
  Show dependency treegraph
 
Reported: 2009-08-10 06:27 PST by
Modified: 2009-09-04 15:50 PST (History)


Attachments
Patch v1 (12.72 KB, patch)
2009-08-21 13:29 PST, Michelangelo De Simone
no flags Review Patch | Details | Formatted Diff | Diff
Patch v.1a (15.07 KB, patch)
2009-08-21 17:46 PST, Michelangelo De Simone
adele: review+
Review Patch | Details | Formatted Diff | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2009-08-10 06:27:24 PST
Support for such attributes should be implemented in WebKit. These attributes do nothing but "deactivate" validation on form elements.
------- Comment #1 From 2009-08-20 22:48:51 PST -------
Sadly, much was lost on this bug due to database corruption.

The key points were: Michelangelo attached a patch for review; eseidel gave it r-, with the following comment:

--- Comment #10 from Eric Seidel <eric@webkit.org>  2009-08-20 17:21:28 PDT ---
(From update of attachment 35234)
These tests look pretty vacuous.  They would pass w/o any of the code changes
it seems.

+v = document.getElementsByName("victim");
+for (i = 0; i < v.length; i++) {
+    shouldBe("v[i].formNoValidate", "false");
+    v[i].formNoValidate = true;
+}
+for (i = 0; i < v.length; i++)
+    shouldBe("v[i].formNoValidate", "true");

Personally I prefer to write js-only tests, instead of making manual templates
as you have done.  Meaning, if you convert your form dom creation into JS
calls, this whole test can just live in a single .js file in resources/ and you
can use make-script-test-wrappers to generate the wrapper for you.

It seems it would be more interesting to test what getAttribute('novalidate')
gets set to when you change the JS properties.
------- Comment #2 From 2009-08-21 13:29:10 PST -------
Created an attachment (id=38391) [details]
Patch v1
------- Comment #3 From 2009-08-21 16:12:33 PST -------
Adele commented about the proposed patch: HTMLFormControlElement::isInNoValidateState() should land once it's being used.

Eliminating it, for now. But it shall be back.:)
------- Comment #4 From 2009-08-21 17:46:01 PST -------
Created an attachment (id=38425) [details]
Patch v.1a
------- Comment #5 From 2009-08-21 18:17:47 PST -------
Fixed in r47655.
------- Comment #6 From 2009-08-21 18:57:53 PST -------
Tree broken, investigating...
------- Comment #7 From 2009-08-21 19:12:44 PST -------
Fixed in r47658.

Committed patch was incomplete, modifications in HTMLFormControlElement.h present in the r+'ed patch were missing.;)