Skip to content

fix(slide-toggle): clear tabindex from host element #13311

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

Merged
merged 1 commit into from
Oct 2, 2018

Conversation

crisbeto
Copy link
Member

Along the same lines as #13308. Currently we forward the tabindex from the host to the underlying input, however we never clear the tabindex from the host, which means that we end up with two layers of focusable elements.

Along the same lines as angular#13308. Currently we forward the `tabindex` from the host to the underlying `input`, however we never clear the `tabindex` from the host, which means that we end up with two layers of focusable elements.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Sep 25, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 25, 2018
crisbeto added a commit to crisbeto/material2 that referenced this pull request Sep 26, 2018
Along the same lines as angular#13311 and angular#13308. Clears the `tabindex` from the radio button host element so we don't end up with multiple tab stops.
@devversion devversion added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Sep 27, 2018
jelbourn pushed a commit that referenced this pull request Sep 27, 2018
Along the same lines as #13311 and #13308. Clears the `tabindex` from the radio button host element so we don't end up with multiple tab stops.
@vivian-hu-zz vivian-hu-zz merged commit 119fafd into angular:master Oct 2, 2018
roboshoes pushed a commit to roboshoes/material2 that referenced this pull request Oct 23, 2018
Along the same lines as angular#13311 and angular#13308. Clears the `tabindex` from the radio button host element so we don't end up with multiple tab stops.
roboshoes pushed a commit to roboshoes/material2 that referenced this pull request Oct 23, 2018
Along the same lines as angular#13308. Currently we forward the `tabindex` from the host to the underlying `input`, however we never clear the `tabindex` from the host, which means that we end up with two layers of focusable elements.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants