feat(mat-menu): Open nested menus should be delayed on hover.
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
### Feature Description
An option to delay the menu of nested items would be great.
This prevents the menus from blinking/flashing when you just hover/move the mouse quickly to another wanted item.
Solution: Add delay before opening the nested menu. Only a few milliseconds to prevent flashing menus when you just move the mouse around. The user can still click on a nested item to trigger the menu instantly. This will improve the UX. It's really annoying if the menus are flashing.
You can test my suggested behavior in other proven menus like in Windows 10. Just open a folder and open the context menu. You'll see that the nested menus don't open immediately. They are delayed. Same behavior in VSCode. A shorter delay than the Windows menus, but they are delayed. And I think we should implement this for the mat-menus too.
|mat-menu| vs-code |
|---|---|
|  |  |
https://material.angular.io/components/menu/examples
Summary:
- Delay nested menu on hover.
- Open nested menu instantly on click.
- Delay nested menu before close (hover leave).
- Implement it with fixed delay time or as an option property with default value (the time in ms. Not just boolean).
Btw: Another related issue which is about delay before closing: #24476
We could combine both issues to add delay before and after.
I think this issue is more a bug than a feature. An unwanted behavior / bad UX. But anyway, it's no candidate for votes. It something what should be considered by the Angular team.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par l’implémentation de mat-menu et l’issue associée concernant le délai de fermeture #24476, puis comparez le comportement demandé avec les exemples de menus Material liés. C’est terminé lorsque les menus imbriqués s’ouvrent après un court délai au survol, s’ouvrent immédiatement au clic, qu’un délai est appliqué avant la fermeture et qu’un délai par défaut fixe ou configurable est exposé.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- frontend
- Type d'issue
- Fonctionnalité
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100