[jira] [Commented] (FLEX-34149) Next features/bugs for spark MaskedTextInput experimental component

["Justin Mclean (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLEX-34149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937372#comment-13937372 ] 

Justin Mclean commented on FLEX-34149:
--------------------------------------

Might be a good idea to make these sub tasks by clicking more create subtask.

> Next features/bugs for spark MaskedTextInput experimental component
> -------------------------------------------------------------------
>
>                 Key: FLEX-34149
>                 URL: https://issues.apache.org/jira/browse/FLEX-34149
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Spark Components
>    Affects Versions: Apache Flex 4.12.0
>            Reporter: Carlos Rovira
>            Assignee: Carlos Rovira
>            Priority: Minor
>              Labels: maskedtextinput
>
> After the release of Flex SDK 4.12 with the new MaskedTextInput component there's some issues and improvements to take into account. This ticket is a placeholder to list all of them:
> 1) Mobile support. Right now the component is based on TextOperationEvent not supported in mobile. So we need to remove this dependency and get it working for both mobile and desktop
> 2) In Actual version,  when different constraint patterns are applied (i.e: ### @@@), when user remove chars this makes some chars occupy invalid positions. This only can be solved maintaining the slots where chars exits and avoid "dragging" chars as user removes some of them, so replacing with blanks.
> 3) Actually there's no support for direction LTR (left to right).
> 4) Support for regex complex patterns  (i.e: for dates, be able to express numbers restrictions to avoid the user to enter numbers that could not be days, months, or years...)
> If there's more issues or features to take into account we can update this ticket to log the needs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)