hi josh
thanks for all your work
its looking good.
a) any chance of getting this to work with the meta data plugin ?
b) any idea when the above (blank input) could be addressed - just
wondering as i need to make a call on wether i use it on a current
project.
many thanks!
sean
hi josh
thanks for all your work
its looking good.
a) any chance of getting this to work with the meta data plugin ?
b) any idea when the above (blank input) could be addressed - just
wondering as i need to make a call on wether i use it on a current
project.
many thanks!
sean
i think personally that indeed a callback onError, that is called when
the input loses focus would be great. from thereon, the user can
defines what to do. for instance, as a UI developer, i would add a
"error" class to the wrapping div, and add "Incomplete data" message
to the right of the input.
Thank you Jörn and Alexandre for your feedback. I'm thinking that
maybe I should just provide a hook that gets called when the plugin
detects invalid input. I could just provide a default function that
blanks the input as it is today, but would let the user decide what to
do there.
Any ideas on
I second that! An option to make the plugin more tolerant, especially
in combination with other forms of validation, would be perfect. Other
changes all sounds fine. The fix for "users typed over existing input"
will be much appreciated.
Thanks
Jörn
On Mon, Dec 22, 2008 at 3:59 PM, Alexandre Plen
Josh, these are very cool additions, love the New mask syntax option '?' and
the improved usability.
Thanks for your hard work!
just noticed in the demo that if i don't fill the input completely and go to
another input, it removes the entered value entirely as soon as the input
loses focus. That's
6 matches
Mail list logo
