Closed
Bug 622558
Opened 15 years ago
Closed 15 years ago
When .setCustomValidity() is used, :-moz-ui-invalid should always apply
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla2.0b10
People
(Reporter: mounir, Assigned: mounir)
References
()
Details
Attachments
(1 file)
|
21.55 KB,
patch
|
sicking
:
review+
sicking
:
approval2.0+
|
Details | Diff | Splinter Review |
1. Open the testcase (URL field), type 'foo'.
2. The input is now invalid but :-moz-ui-invalid doesn't apply.
3. Un-focus the text field: now :-moz-ui-invalid applies.
Expected results: 2. should be "The input is invalid and :-moz-ui-invalid applies."
|
Assignee | |
Comment 1•15 years ago
|
||
This patch makes :-moz-ui-invalid always apply when an element suffers from a custom validity. Actually, even if novalidate has been set. I don't know if that's what we want but I'm going to open a bug for novalidate so I will take a decision in this bug.
|
|
Assignee | |
Updated•15 years ago
|
Whiteboard: [needs-review]
|
|
Assignee | |
Updated•15 years ago
|
Whiteboard: [needs-review] → [needs-review][passed-try]
Attachment #500836 -
Flags: review?(jonas)
Attachment #500836 -
Flags: review+
Attachment #500836 -
Flags: approval2.0+
|
|
Assignee | |
Updated•15 years ago
|
Whiteboard: [needs-review][passed-try] → [needs-landing][passed-try]
|
|
Assignee | |
Comment 3•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: [needs-landing][passed-try]
Target Milestone: --- → mozilla2.0b10
You need to log in
before you can comment on or make changes to this bug.
Description
•