Re: Re: HTML_QuickForm DHTML client rules and SoftRequired rule

On 3/27/06, Mark Wiesemann <wiesemann@php.net> wrote: > Justin Patrin wrote: > > > But you did. You gave the element focus (tabbing to it or clicking on > > it), then took the focus away (tabbing out of it or clicking > > elsewhere). > > No. Just try yourself: Put the cursor into the second form field. Then > hit the tabular key and see what happens. I've tested it with IE 6 and > Firefox 1.5 and got immediately the question. This is not what I (and > maybe also you) expect. > Aha, I see. I didn't realize this had happened. This was due to the onKeyUp event. I've commented this out for now as people seem not to like it in general. > > This constitues interacting with the element. Since you've > > interacted with the element but not done anything, it lets you know > > that there is a potential problem. > > In the way you describe it, the behavior is okay and the question makes > sense. > > > Again, this is more of a question of opinion. When would you like the > > error checking to happen? If not onBlur or onKeyUp, the only > > possibility left is onSubmit (unless you want to do it onMouseOver or > > onMouseOut, which I doubt). If you leave validation to onSubmit then > > you can have the other problems I've outlined. IMHO it's better to at > > least have the onBlur as it lets the user know, right after they've > > filled out the form, that they need to fix something. > > Your point is valid, although I like these "early" messages not that > much. I will play with your code in the next days and look for a > solution that makes me really happy. ;-) > Sounds good. -- Justin Patrin