From: Katana <ka...@ka...> - 2004-05-23 14:04:16
|
> With that there's no need to save fields on validation imho but it might > be usefull bc and some people might want that feature. > So what do you think about a global formsess option 'saveOnValidate'? > (i already added that but i can be changed of course) > > Similar to that i would also like to add a 'unsaveOnFailedCheck' option. Yes, both sounds good. How / where do we set / store these options ? > I think for the beginning it would be sufficient to adjust that things > on form level rather than on every single field. > We could still add an attribute that changes the same thing for a single > field but i would prefer to concentrate on getting ready to release > rather than adding more and more features. Yes, global is ok. > We still didn't get any further with the password field. > What do you think, should we add an attribute or just another global > formsess option ('keepPassordFields')? > I'd prefer the seccond. The 2nd is ok with me. Making it false by default should match most users requirements. Katana |