-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Menu with matMenuContent breaks hover behaviour #16954
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Sep 3, 2019
Currently in some cases we restore focus immediately and in others we wait for the exit animation to finish (when using `matMenuContent`) because the focus restoration logic is coupled to the menu cleanup. This means that if multiple animations overlap, we could end up restoring focus to the wrong element. These changes switch to restoring focus immediately in all cases. Fixes angular#16954.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Sep 3, 2019
Currently in some cases we restore focus immediately and in others we wait for the exit animation to finish (when using `matMenuContent`) because the focus restoration logic is coupled to the menu cleanup. This means that if multiple animations overlap, we could end up restoring focus to the wrong element. These changes switch to restoring focus immediately in all cases. Fixes angular#16954.
jelbourn
pushed a commit
that referenced
this issue
Sep 6, 2019
Currently in some cases we restore focus immediately and in others we wait for the exit animation to finish (when using `matMenuContent`) because the focus restoration logic is coupled to the menu cleanup. This means that if multiple animations overlap, we could end up restoring focus to the wrong element. These changes switch to restoring focus immediately in all cases. Fixes #16954.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Sep 7, 2019
Currently in some cases we restore focus immediately and in others we wait for the exit animation to finish (when using `matMenuContent`) because the focus restoration logic is coupled to the menu cleanup. This means that if multiple animations overlap, we could end up restoring focus to the wrong element. These changes switch to restoring focus immediately in all cases. Fixes angular#16954.
jelbourn
pushed a commit
that referenced
this issue
Sep 9, 2019
Currently in some cases we restore focus immediately and in others we wait for the exit animation to finish (when using `matMenuContent`) because the focus restoration logic is coupled to the menu cleanup. This means that if multiple animations overlap, we could end up restoring focus to the wrong element. These changes switch to restoring focus immediately in all cases. Fixes #16954.
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
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Reproduction
https://stackblitz.com/edit/angular-nzsa6j?file=app/nested-menu-example.html
Steps to reproduce:
It only happens for menu items with trigger it seems
Expected Behavior
What behavior were you expecting to see?
The hover functionality should work the same as without the matMenuContent
Actual Behavior
What behavior did you actually see?
The hover functionality isn't working as expected and highlighting more than one element (even with slight delay it seems)
Environment
The text was updated successfully, but these errors were encountered: