Bug 149832 (minlength)
Summary: | Add support for input[minlength], textarea[minlength], and ValidityState.tooShort | ||
---|---|---|---|
Product: | WebKit | Reporter: | Chris Rebert <webkit> |
Component: | Forms | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | derek.p.moore, kai.hollberg, mkhatib727 |
Priority: | P2 | Keywords: | HTML5 |
Version: | WebKit Nightly Build | ||
Hardware: | All | ||
OS: | All | ||
URL: | https://html.spec.whatwg.org/multipage/forms.html#attr-input-minlength | ||
See Also: | https://bugzilla.mozilla.org/show_bug.cgi?id=932755 |
Chris Rebert
i.e. Implement the `minlength` attribute
Relevant specs:
* https://html.spec.whatwg.org/multipage/forms.html#attr-input-minlength
* https://html.spec.whatwg.org/multipage/forms.html#attr-textarea-minlength
* https://html.spec.whatwg.org/multipage/forms.html#dom-validitystate-tooshort
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Derek Moore
Don't feel bad, Firefox is also sucking at implementing this: https://bugzilla.mozilla.org/show_bug.cgi?id=932755
Chris Rebert
For the record, Blink implements this:
http://caniuse.com/#feat=input-minlength
Derek Moore
FWIW, you'll be way ahead of both Chrome/Blink & Mozilla/Firefox if you can make minlength & maxlength work together so as to form a character length range (as per spec)!
See the "Name of Event" example here: https://html.spec.whatwg.org/multipage/forms.html#attr-fe-minlength
Derek Moore
(In reply to comment #2)
> For the record, Blink implements this:
> http://caniuse.com/#feat=input-minlength
Logged this bug with them for completeness:
https://bugs.chromium.org/p/chromium/issues/detail?id=614175
Chris Rebert
Firefox has implemented this feature in version 51.
Kai
Probably fixed by https://bugs.webkit.org/show_bug.cgi?id=161644 ?
Not sure about ValidityState.tooShort, in the diff https://bugs.webkit.org/attachment.cgi?id=288065&action=diff it seems to be at least mentioned.
Chris Rebert
*** This bug has been marked as a duplicate of bug 161644 ***