Steps to reproduce
- Open the attached testcase webpage in Edge.
- Observe the colors of the outlines of the
What is the expected behavior?
The outlines should be green, indicating that the
<input type=number>s did not match the
What went wrong?
The outlines are orange and red, indicating that the
<input type=number>s matched the
Comments and activity
Based on my reading of the HTML spec,
:out-of-rangeshould never apply to
:in-rangepseudo-class must match all elements that are candidates for constraint validation, have range limitations, and […]
:out-of-rangepseudo-class must match all elements that are candidates for constraint validation, have range limitations, and […]
A submittable element is a candidate for constraint validation except when a condition has barred the element from constraint validation.
If the readonly attribute is specified on an input element, the element is barred from constraint validation.
If an element is disabled, it is barred from constraint validation.
readonly``s are barred from constraint validation, meaning they are not candidates for constraint validation, thus causing them to be disqualified by the 1st of the 3 conditions which are required for an element to match
- Microsoft Edge Team
Changed Assigned To to “Bogdan B.”
Changed Assigned To from “Bogdan B.” to “Rossen A.”
Changed Status to “Confirmed”
The bleeding-edge versions of Firefox, Chrome, and Safari no longer suffer from the same bug. See note #3 on http://caniuse.com/#feat=css-in-out-of-range