Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[igxMask] to include TabNavigation through the mask #6421

Closed
NickCook-StruMIS opened this issue Jan 7, 2020 · 3 comments
Closed

[igxMask] to include TabNavigation through the mask #6421

NickCook-StruMIS opened this issue Jan 7, 2020 · 3 comments

Comments

@NickCook-StruMIS
Copy link

NickCook-StruMIS commented Jan 7, 2020

Hi,

I am trying to use the [igxMask] directive to implement an Imperial length component. For Example: 12'6-3/4"

The [igxMask] works very well but unfortunately you cannot control moving to the next section of the mask via tab navigation (arrow navigation only). Tabbing on the control calls the blur function and moves focus to the next control.

I would like to know if there are any plans to implement tab navigation through the [igxMask] directive. Our customers will expect this behaviour as they are used to it in our current released product which uses Infragistics Win controls.

I have tried using focusValuePipe and displayValuePipe but can't get the required behaviour.
I could also create my own control with 4 individual [igxMask] directives for (Foot, Inch, Numerator & Denominator). But would prefer a more elegant solution using one [igxMask]

Thanks.

@Lipata
Copy link
Member

Lipata commented Jan 7, 2020

Hi, @NickCook-StruMIS.

We have initiated improvements related to our input components. The first item, which is to create a separate date editor directive, involves changes on the mask as well. When we create the specification we will define navigation through the mask/date-editor parts and I guess we will choose or at least will use as a start point the HTML input type date functionality, which will navigate using keyboard arrows. The main purpose of the TAB key is to navigate through elements in a form, which will mean that we will prefer the arrows for navigation inside the input. Please tell me what you think.

@NickCook-StruMIS
Copy link
Author

Hi, @Lipata

Ok, I understand the need to keep the tab for moving to the next element on the form. We found it better to use separate elements in our component in the end to get more control and each element has its own [igxMask] settings.

Thanks for your help, no further enhancement is needed.

@Lipata
Copy link
Member

Lipata commented Jan 14, 2020

Hi, @NickCook-StruMIS.

I think your solution is good. Note that in the igxMask you can navigate through different sections, using Ctrl + Arrow Left/Right. Looking for other components suits I don't see a mask editor that supports different navigation different from the one that I mentioned, so I'm not sure which will be the best UX approach in that case.

In the context of a date editor, as I mentioned earlier, we think the HTML input type date functionality is a good approach.

@Lipata Lipata added ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged. ❓ question and removed 🆕 status: new 🧰 feature-request ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged. labels May 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants