Some Mat SVG Icons disappear on mat-sidenav close
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
#### Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/edit/angular-7-master-svg1
Steps to reproduce:
1. Setup shared components for svg icon, sidebar content and page content alongside the ability to toggle mat-sidenav.
2. Toggle Sidenav and see all svg icons on the page get disappeared on sidenav close and re-appear on sidenav open.
#### Expected Behavior
No svg icon should disappear from the page.
#### Actual Behavior
Toggling Sidenav makes all svg icons on the page disappear on sidenav close and re-appear on sidenav open. Moreover, if you inspect the html output of page and components, you will see that svg icons are still present there, with no change in attributes, html, etc. Furthermore, this bug happens with some icons only (not sure what is the differentiator as there's dozens of icons in our locally under-development app that exhibit this weird bug, but there are also some that don't), for example, svg icon in this stackblitz works correctly. https://stackblitz.com/edit/angular-7-master-svg2
#### Environment
- Angular: 7.2.8
- CDK/Material: 7.3.3
- Browser(s): Google Chrome Version 75.0.3770.100 (Official Build) (64-bit) and Version 71.0.3578.80 (Official Build) (64-bit)
- Operating System (e.g. Windows, macOS, Ubuntu): Cent OS and Windows 10
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par les deux reproductions StackBlitz liées, angular-7-master-svg1 et angular-7-master-svg2, et comparez le comportement de basculement de mat-sidenav avec les icônes SVG. Suivez l’interaction entre mat-sidenav et les icônes SVG Material, puis vérifiez que le basculement de sidenav laisse toutes les icônes SVG visibles, y compris les icônes qui disparaissent actuellement.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- frontend
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100