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

TabIndex issue #8078

Closed
Andree643 opened this Issue Apr 15, 2015 · 6 comments

Comments

Projects
None yet
3 participants
@Andree643

When I try to exclude the form element from tab flow, the tabindex attribute is ignored.
See the example bellow.

http://codepen.io/Andree643/pen/raXdEb

@gabrielschulhof

This comment has been minimized.

Show comment
Hide comment
@gabrielschulhof

gabrielschulhof Apr 15, 2015

Contributor

@Andree643 Can you please reproduce this problem with our latest code? http://jsbin.com/huvoraba/1/edit provides a great starting point.

Contributor

gabrielschulhof commented Apr 15, 2015

@Andree643 Can you please reproduce this problem with our latest code? http://jsbin.com/huvoraba/1/edit provides a great starting point.

@Andree643

This comment has been minimized.

Show comment
Hide comment

Here is the problem on jsBin

http://jsbin.com/mirupigade/2/

@arschmitz

This comment has been minimized.

Show comment
Hide comment
@arschmitz

arschmitz Apr 16, 2015

Member

The problem is we are not copying the tab index from the native select. To the new select.

Member

arschmitz commented Apr 16, 2015

The problem is we are not copying the tab index from the native select. To the new select.

@Andree643

This comment has been minimized.

Show comment
Hide comment
@Andree643

Andree643 Apr 16, 2015

I can see that. Isn't this possible to implement this feature? In my opinion this is quite useful since you can use forward/backward tabbing among the fields in eg. Apple devices.

I can see that. Isn't this possible to implement this feature? In my opinion this is quite useful since you can use forward/backward tabbing among the fields in eg. Apple devices.

@arschmitz

This comment has been minimized.

Show comment
Hide comment
@arschmitz

arschmitz Apr 16, 2015

Member

@Andree643 yes it is and yes it should be there, but we have to identify and confirm the cause of an issue before we can fix it.

Member

arschmitz commented Apr 16, 2015

@Andree643 yes it is and yes it should be there, but we have to identify and confirm the cause of an issue before we can fix it.

@Andree643

This comment has been minimized.

Show comment
Hide comment
@Andree643

Andree643 Apr 16, 2015

@arschmitz So this feature should be already present, but there is a bug if I understand it correctly.

@arschmitz So this feature should be already present, but there is a bug if I understand it correctly.

@arschmitz arschmitz self-assigned this Jun 29, 2015

arschmitz added a commit that referenced this issue Jul 8, 2015

@arschmitz arschmitz closed this Jul 8, 2015

arschmitz added a commit to arschmitz/jquery-mobile that referenced this issue Jul 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment