checkValidity issue
Reported by
jjtu...@gmail.com,
Oct 13 2016
|
|
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36 Steps to reproduce the problem: 1. At first, textarea has non null value and it's validity is true (no red border) 2. Set textarea's value to null (remove the text) and it's validity will be false (red border is present) 3. Write any text in textarea What is the expected behavior? Textarea's validity should be again true (there should be no red border) What went wrong? Textarea's validity is still false even though it is non empty Did this work before? No Does this work in other browsers? No There is a same issue in FF ( https://bugzilla.mozilla.org/show_bug.cgi?id=1309805 ). Same workaround doesn't work there. Chrome version: 53.0.2785.101 Channel: n/a OS Version: 4.7.2-101.fc23.x86_64 Fedora Flash Version: Shockwave Flash 22.0 r0 Here is jsFiddle with an example https://jsfiddle.net/buksy/4tsd8dw8/ . There is a workaround for this bug when tested textarea is first deep cloned and the clone is tested instead of the original one. (PS OT: When I'm here, I would love to also notice that Backspace bug hasn't been resolved till this day :(.) |
|
►
Sign in to add a comment |
|
Comment 1 by tkent@chromium.org
, Oct 14 2016Owner: tkent@chromium.org
Status: WontFix (was: Unconfirmed)
It works as intended. checkValidity(e) in your code calls setCustomValidity(non-empty-srring). After that, checkValidity() is always false, and your code never call setCustomValidity("").