On Mon, 24 Sep 2007 08:25:54 +0200, Mark Birbeck <mark.birbeck@formsPlayer.com> wrote: > I think the @constraint way is the best one. I agree. Apart from it being the shortest, the reason I prefer the constraint approach over HTML's maxlength is that it records everything I type. When I type I don't necessarily watch the screen while I do it. With the maxlength version, the text after the maxlength is just lost (and if I don't look I may not even notice). The constraint approach keeps the text I typed, with a visual indication that something is wrong, and preventing me from submitting the data. I can then go and edit the offending field to reduce it to size: the text that I want to keep may be at the end of the field rather than the beginning. Small case in point: When I type in my address in a form, I usually 'type blind' and tab from field to field. Dutch postal codes consist of 4 digits, a space and 2 letters. However some wretched sites don't accept the space, and have a maxlength of 6 on the field. I type "1234 AA", and tab out, and the field contains "1234 A". Now I have to delete the space and type another A. The constraint version would have let me just delete the space. Best wishes, Steven PembertonReceived on Monday, 24 September 2007 08:45:04 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 October 2007 16:02:02 GMT