Opened 12 years ago
Closed 5 years ago
#8192 closed enhancement (patchwelcome)
ValidationTextBox: display more descriptive error messages
Reported by: | Scott Lewis | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | 1.13 |
Component: | Dijit - Form | Version: | 1.2.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Error messages should be better tailored to the problem AND built into the validator type. Look at Flex validators (http://examples.adobe.com/flex3/componentexplorer/explorer.html) for an example of appropriate error messages.
Change History (11)
comment:1 Changed 12 years ago by
Type: | defect → enhancement |
---|
comment:2 follow-up: 3 Changed 12 years ago by
I did look under the link above, in the "Validators and Formatters" section, but upon entering an invalid value the only thing that happens is that it turns red... I don't see any error message appear at all. Did I miss something?
comment:3 Changed 12 years ago by
Replying to bill:
I did look under the link above, in the "Validators and Formatters" section, but upon entering an invalid value the only thing that happens is that it turns red... I don't see any error message appear at all. Did I miss something?
SL: Try email validator. Omit the @ sign. The field turns red. Hover over the field. The message is provided in an tooltip. The message is very specific ie. "The at sign (@)is missing in your email address." This tells the user exactly what is wrong.
comment:4 Changed 12 years ago by
Component: | Dijit - LnF → Dijit |
---|---|
Milestone: | tbd → 1.4 |
Summary: | ValidationTextBox → ValidationTextBox: display more descriptive error messages |
Ah I see, I didn't try hovering.
Yes, flex has much better messages then us, I see your point.
This would be a big change to our infrastructure (currently the code just works off of a regular expression), but I can see the value.
Let's try to do this for 1.4.
comment:5 Changed 12 years ago by
Interesting. Well, I'd rather see us implement hints in our UI (#3286). I'm not sure error messages like the ones in Flex are always that useful. For example, for incomplete responses like:
[email protected] -> "the domain in your e-mail address is missing a period" (well, there is no host/domain. Do non-technical users know what a domain is? etc.)
bar.com -> "An at-sign (@) is missing in your e-mail address". Well, so is the username.
and so on. I guess it all depends on how complex your heuristics are. I'd rather try hinting, keep the regexp mechanism, and show "this is not a valid e-mail address, like [email protected]…" It's simple, to the point, and we know it's right.
comment:6 Changed 11 years ago by
Milestone: | 1.4 → 1.5 |
---|
comment:7 Changed 11 years ago by
Milestone: | 1.5 → future |
---|
comment:8 Changed 10 years ago by
Component: | Dijit → Dijit - Form |
---|---|
Owner: | set to Douglas Hays |
comment:9 Changed 7 years ago by
Owner: | Douglas Hays deleted |
---|---|
Status: | new → assigned |
comment:10 Changed 7 years ago by
Status: | assigned → open |
---|
comment:11 Changed 5 years ago by
Milestone: | future → 1.12 |
---|---|
Resolution: | → patchwelcome |
Status: | open → closed |
Given that no one has shown interest in creating a patch in the past 5+ years, I'm closing this as patchwelcome.
Please provide specific information and/or examples