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 has been archived by the owner on May 29, 2019. It is now read-only.
Just for clarity, what would your preferred solution be? Would it be for the individual inputs to also inherit the same tabindex (i.e. 8 in this example)?
@wesleycho Yes, all the individual inputs should get the same tabindex. Elements with the same tabindex are processed in the order they appear. The outer element should not have a tabindex.
I'm not using the up/down links, which is what I believe you're referring
to. But yes, for accessibility purposes they should be on those links as
well.
On Sun, Oct 11, 2015 at 9:53 AM, Wesley Cho [email protected]
wrote:
This means that the tabindex should also be on the links as well.
—
Reply to this email directly or view it on GitHub #4569 (comment)
.
When specifying tabindex on timepicker without spinners
<uib-timepicker show-spinners="false" tabindex="8" />
the surrounding table around timepicker is highlighted when getting to the corresponding tabindex, and not the individual inputs. Using Chrome on Mac.
When tabindex is specified, I'd like to see this same tabindex applied to each of the individual input fields of timepicker.
The text was updated successfully, but these errors were encountered: