New issue
Advanced search Search tips

Issue 883723 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
swarnasree.mukkala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

required single radio buttons don't validate when created dynamically

Reported by bolde...@gmail.com, Sep 13 
UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to reproduce the problem:
1. Create an input element, type=radio, that's unchecked and required
2. Inspect input.validity.valueMissing
3. The value should be true. The input is not checked but required

What is the expected behavior?

What went wrong?
The value of input.validity.valueMissing is false.

The behavior is correct for nodes already present in the HTML source, see <https://jsbin.com/curasa/edit?html,js,console,output>.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 69.0.3497.92 (Offizieller Build) unknown (64-Bit)  Channel: stable
OS Version: Ubuntu 18.04
Flash Version: 31.0.0.108

Corresponding WHATWG HTML spec: https://html.spec.whatwg.org/multipage/input.html#radio-button-state-(type=radio)

Corresponding W3C HTML 5.2 spec: https://www.w3.org/TR/html5/sec-forms.html#radio-button-state-typeradio
radio_required_bug.html
375 bytes View Download

Comment 1 by bolde...@gmail.com, Sep 13 

Notes:

* works in Firefox 62.0 and Edge 17
* still doesn't work, when the element is inserted into a form, i.e., part of a “real” radio button group

Comment 2 by krajshree@chromium.org, Sep 14

Labels: Needs-Triage-M69

Comment 3 by hayato@chromium.org, Sep 14

Components: -Blink>DOM Blink>Forms>Radio

Comment 4 by swarnasree.mukkala@chromium.org, Sep 14

Cc: swarnasree.mukkala@chromium.org
Labels: Triaged-ET Target-71 M-71 FoundIn-71 OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on chrome version #60.0.3112.20 reported chrome version #69.0.3497.92 and on latest canary#71.0.3552.2 on Ubuntu 17.10, Mac OS 10.13.6 and Windows 10.

This is a non-regression issue and the behavior is seen from old M-60 builds, hence marking it as untriaged and requesting someone from the dev team to kindly look into the issue.
Thanks.!

Comment 5 by tkent@chromium.org, Sep 18

Labels: -Pri-2 -M-71 -Needs-Triage-M69 -Target-71 Pri-3
Status: Available (was: Untriaged)
I guess it's not easy to fix validation of a disconnected required radio button. However it should be easy to fix validation on connecting it to a document.
►

Sign in to add a comment