Opened 11 years ago

Last modified 5 years ago

#13205 open enhancement

[patch][cla] InputMask for dijit.form.TextBox / dijit.form.ValidationTextBox

Reported by: Florian Owned by:
Priority: high Milestone: 1.15
Component: Dijit - Form Version: 1.7.0b1
Keywords: Cc:
Blocked By: Blocking:



is there a chance to implement support for input-masks with dijit.form.TextBox? / dijit.form.ValidationTextBox?, e.g. like in meioMask (

With an input-mask like "00.00.0000", the user for example could input a date "09.06.2011" (german format) as "09062011" (or even better as "090611" in a DateTextBox? with constraint fullYear = false), and the dots would automatically be inserted when typing.



Change History (8)

comment:1 Changed 11 years ago by Douglas Hays

Milestone: tbdfuture

Waiting for an implemention patch file and automated doh.robot testcase...

comment:2 Changed 8 years ago by Douglas Hays

Owner: Douglas Hays deleted
Status: newassigned

comment:3 Changed 8 years ago by Douglas Hays

Status: assignedopen

comment:4 Changed 7 years ago by dylan

Milestone: future1.11
Summary: InputMask for dijit.form.TextBox / dijit.form.ValidationTextBox[patch][cla] InputMask for dijit.form.TextBox / dijit.form.ValidationTextBox

comment:5 Changed 7 years ago by dylan

For the patch in comment 4:

I would recommend adding a pull request at via the contributing guidelines at

For what it's worth, your approach is similar to what our team has done for this (listen for input events, and only allow the event to happen if the new value entered is valid).

One issue I see with your patch is that it expected _partialre, but this is only defined for ValidationTextBox?, and not for TextBox?. It would also help to have some source code comments, and some tests added, before this is considered for 1.11.

comment:6 Changed 6 years ago by dylan

This is probably a worthwhile addition since it's such a common pattern, if anyone has time/interest in refining a PR for it.

comment:7 Changed 6 years ago by dylan

Milestone: 1.111.12

comment:8 Changed 5 years ago by dylan

Milestone: 1.131.15

Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.

Note: See TracTickets for help on using tickets.