#11181 closed defect (bug) (fixed)
.form-invalid remains on .form-field in IE after onchange
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 2.9 | Priority: | normal |
Severity: | normal | Version: | 2.9 |
Component: | JavaScript | Keywords: | has-patch |
Focuses: | Cc: |
Description
In IE 6, 7 & 8 javascript change events won't get fired on .form-field so they need to be on an <input>. If there is an invalid form the red error style remains on input fields in IE even when the error has been corrected.
How to reproduce for Categories that already exist
- Using IE Go to Admin->Posts->Categories
- Submit form with category name that already exists (error should appear)
- Change content in category name to something that doesn't exist and submit the form (error should go away but it doesn't)
How to reproduce for Categories with no name
- Using IE Go to Admin->Posts->Categories
- Submit form with no category name (error should appear)
- Enter content in category name and tab out of field (error should go away but it doesn't)
How to reproduce for Tags with no name
- Using IE Go to Admin->Posts->Post Tags
- Submit form with no tag name (error should appear)
- Enter content in tag name and tab out of field (error should go away but it doesn't)
I'm not even sure why I was using IE but I thought I'd try to fix this...
Attachments (3)
Change History (8)
#3
in reply to:
↑ 2
;
follow-up:
↓ 4
@
15 years ago
Replying to azaozz:
I noticed that you changed .parents() to .closest(). I actually tried closest when I was working on the patch and ran some test code with the firebug profiler. Turns out that parents() is faster in that particular case and runs less queries. I've attached the test code in case you're interested.
Note: See
TracTickets for help on using
tickets.
(In [12215]) Fix removal of .form-invalid in IE, props aldenta, fixes #11181