I have done some research on cfselect validation being useless but I have a hard time believing it. I have tested it on my own and cannot get the tag to work.
All the other cf validation works (cftextarea, cfinput, etc). Just not on the cfselect field.
It is working, just not the way you are thinking. The built in validation does not care about the option "values". It only checks that _some_ option is selected, regardless of the "value". As Ian pointed out, something IS selected. So there is no error.
If you look at the internal javascript used for cfselect validation it is really geared towards multiple selection lists. Not single (as you are using). So you may need to write your own validation.
I already implemented the fix WTG mentions which has allowed the validation to work for a long time now.
However suddenly a few people are "sneaking through" the validation and I don't know why. I get error notifications and so far the only common thread I see is that they are running IE8 (most of our users are still on IE6 but we are slowly upgrading).
When I try the problem page with an IE8 browser the validation works as expected... so I cannot reproduce the error. But there is an error nonetheless.
There must be more to the story but I'm still looking for it.
I recently struggled with getting this to work on two separate projects. I ended up relying on the server side validation, but I'd rather have the client first because I think it makes for a better interface.
Thanks for posting this. It helped me out in both spots!
8
Replies
AdChoices