Closed
Bug 1092057
Opened 10 years ago
Closed 10 years ago
required field error doesn't work in the blank field w/ cursor
Categories
(Mozilla Foundation Communications :: Website, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: andrea, Assigned: thecount)
References
Details
(Whiteboard: [EOYFR2014][donation flow][nov14])
Firefox: Whatever field my cursor is sitting in when I hit "Donate now" does not highlight in red, even if it's blank+required. See postal code box, incomplete, not highlighted in red here: example A: http://note.io/1wjoPYu and another example: http://note.io/1wjp7Pb
Assignee | ||
Updated•10 years ago
|
Assignee: aki → scott
Assignee | ||
Comment 1•10 years ago
|
||
Interesting, I'll see what I can do. It's a conflict between selected/error states. Selected adds a blue border, error adds a red, selected overrides error states. I can reverse it, but I don't think that's really complete. I'm thinking what would be ideal is the most recent state is the one that is displayed. Clicking or focusing on an input maybe should clear the error state.
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•10 years ago
|
||
I got another report of this error from someone else doing QA, i'm thinking we should change to error trumps selected. Possible?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•10 years ago
|
||
Andrea: then there's no way of seeing which form field is selected. I strongly recommend not doing that. Scott: One thought would be to give error:focus a red box shadow that further blurs the outline so it's obvious it's selected? Idk if that's possible or not.
Comment 4•10 years ago
|
||
* [oct31] is now past. Please update whiteboard to [nov14] or future train.
Updated•10 years ago
|
Whiteboard: [EOYFR2014][donation flow][oct31] → [EOYFR2014][donation flow][nov14]
Reporter | ||
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•