-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[Tabs] Tab focus change not reported initially when tab-key navigating to tabs component #14142
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
Labels
area: material/tabs
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
I also for some reason can't get (focus) or (blur) to work on any tab related component. Is this intentional? |
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 5, 2019
Fixes the `focusChange` output not emitting when the user tabs into a tab header which is different from the previously-focused one. Fixes angular#14142.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 5, 2019
Fixes the `focusChange` output not emitting when the user tabs into a tab header which is different from the previously-focused one. Fixes angular#14142.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
May 19, 2019
Fixes the `focusChange` output not emitting when the user tabs into a tab header which is different from the previously-focused one. Fixes angular#14142.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Dec 24, 2019
Fixes the `focusChange` output not emitting when the user tabs into a tab header which is different from the previously-focused one. Fixes angular#14142.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 5, 2020
Fixes the `focusChange` output not emitting when the user tabs into a tab header which is different from the previously-focused one. Fixes angular#14142.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 21, 2020
Fixes the `focusChange` output not emitting when the user tabs into a tab header which is different from the previously-focused one. Fixes angular#14142.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area: material/tabs
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Bug, feature request, or proposal:
Bug
What is the expected behavior?
I get always notified when the tab focus changes.
What is the current behavior?
I can
And I get notified when user uses the arrows to navigate the focus left or right, but I do not get notified initially when the whole component is focused by user using the tab-key to enter it.
What are the steps to reproduce?
Stackblitz here w/ instructions:
https://stackblitz.com/edit/angular-material2-issue-i5xfe7?file=app/app.component.html
What is the use-case or motivation for changing an existing behavior?
I need to know when tabs get focus, and I do, the only exception is if the user focuses the first tab by tabbing to it. Note that I'm not interested in the selected tab, but the tab that currently has focus.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All
Is there anything else we should know?
Awesome project, keep up the good work!
The text was updated successfully, but these errors were encountered: