Actually, there currently isn't a programmatic way to set the value
and have it be masked automagically for the developer. I just wanted
to see if I could hook into existing methods to keep from having to
add too much syntax. It's driven off of focus,blur,keypress and
pasting(on certain browsers). I guess if a developer wants to mask
their val they could call .val("something").blur() and everything
would work out like I'm describing, it's just not as terse. :)
Thanks for input.
Josh
On Jun 12, 3:55 pm, "Dan G. Switzer, II" <[EMAIL PROTECTED]>
wrote:
> >That's kind of what I was thinking. I was hoping that their might be
> >a better way.
>
> I'd advise against doing that by default. I suppose you could add it as
> config option for those users that might not have any control over how the
> field is being updated.
>
> I would think that would be exception though. I'd just expect people who are
> using the masked input plug-in to use your method for updating the field
> with a new value.
>
> -Dan
