You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
The tabindex attribute is not being set correctly on text inputs if it is set on a mdTextFloat. Some of what I'm seeing is partially due to including ngAria, but I believe the problem is in tabindex propagation inside mdTextFloat.
In my sample code I am attempting to set the tabindex on the mdButton so that it is last in the tab order. That way the keyboard user can just tab into the form at the first field, enter values, tab thru the form, and finally tab to the Save button and save.
However, it does not work as expected. I have set up this sample code:
Note the tabindex attribute on the md-input-groups somehow manage to get the value of 1 -1! This should be either undefined or -1 to keep them out of the tab order entirely.
The inputs themselves have tabindex="0", which should be 1 set by the mdTextFloat directive based on the original markup. 0 puts elements last in the order after any element with a positive tabindex.
For this to work as expected, the output should be:
npm -> yarn
more updates from Angular Material -> Angular Components
add details on material2-docs-content repo
correct development setup steps
Fixesangular#578. Closesangular#583.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
tabindex
attribute is not being set correctly on text inputs if it is set on amdTextFloat
. Some of what I'm seeing is partially due to including ngAria, but I believe the problem is intabindex
propagation insidemdTextFloat
.In my sample code I am attempting to set the
tabindex
on themdButton
so that it is last in the tab order. That way the keyboard user can just tab into the form at the first field, enter values, tab thru the form, and finally tab to theSave
button and save.However, it does not work as expected. I have set up this sample code:
which behaves as follows as shown in the animated GIF (one frame per Tab keypress):
The markup that was generated was:
Note the
tabindex
attribute on themd-input-group
s somehow manage to get the value of1 -1
! This should be either undefined or-1
to keep them out of the tab order entirely.The
input
s themselves havetabindex="0"
, which should be1
set by themdTextFloat
directive based on the original markup.0
puts elements last in the order after any element with a positive tabindex.For this to work as expected, the output should be:
The text was updated successfully, but these errors were encountered: