[
https://issues.apache.org/jira/browse/WICKET-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536203
]
Will Hoover commented on WICKET-1085:
-------------------------------------
Seeing that the only issue that exists is in relation to prefilled "invalid"
values...
IMHO, I think that it can/should be done generically on the TextField
component. All that would be needed is to verify that a valid regexp validator
exists that supports the mask (remove reserved characters: "9", "L", "l", "A",
and any characters that exist between the reserved regexp character "X").
Basically, this is how a type definition is declared on the TextField to begin
with (minus the mask check)- is it not?
Otherwise, a MaskTextField is fine, but I think it's just as easy to do it
generically :o)
> Input Text Mask
> ---------------
>
> Key: WICKET-1085
> URL: https://issues.apache.org/jira/browse/WICKET-1085
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-extensions
> Reporter: Will Hoover
> Assignee: Frank Bille Jensen
> Priority: Trivial
> Attachments: inputTextMask.js
>
>
> Allow developers to designate a keystroke input pattern for the input text
> component. The pattern would be used on the client to control valid
> keystrokes for the current cursor position within the input text field in
> relation to the specified pattern.
> For example, a pattern could be designated as "(999)-9999" causing only
> number values in each position where a "9" appears and using the "(", ")",
> and "-" as masking characters. When the cursor position reached one of these
> mask characters the cursor position would advance to the next "9" position.
> The resulting mask would appear as "(___)___-____" within the input text
> value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
