Some Mat SVG Icons disappear on mat-sidenav close
- Vorherrschende Sprache
- TypeScript
- Sterne
- 25k
- Forks
- 6.8k
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 91
Beschreibung
#### 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
Beitragsleitfaden
Rechercherichtung
Beginne mit den beiden verlinkten StackBlitz-Reproduktionen angular-7-master-svg1 und angular-7-master-svg2 und vergleiche das Umschaltverhalten von mat-sidenav mit den SVG-Symbolen. Verfolge die Interaktion zwischen mat-sidenav und den Material-SVG-Symbolen und überprüfe anschließend, dass das Umschalten von sidenav jedes SVG-Symbol sichtbar lässt, einschließlich der Symbole, die derzeit verschwinden.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- frontend
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100