ability to manually control overlay's z-index
- Vorherrschende Sprache
- TypeScript
- Sterne
- 25k
- Forks
- 6.8k
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 91
Beschreibung
This would be handy for both user created overlays, as well as those used by angular components such as md-menu.
Take this for example http://plnkr.co/edit/AqjYdsScCYPlK9w44aHQ?p=preview you have a fixed element(some sort custom toolbar), inside it you have a button which triggers md-menu, it works fine, but the `md-menu-click-catcher`, which is for some reason inside the actual `md-menu` element, is actually stacked above `md-overlay-container`, causing any attempt to click on the menu items to close the menu(which can be extremely confusing).
1. `md-overlay-container` should _not_ have z-index at all, as it renders z-indexes of `md-overlay-pane` useless
2. you should be able to manually control z-index of `md-overlay-pane`
I imagine(at least for the user invoked overlay), it could work either by being able to give the overlay my own identificator(class at least), or being able to set it via `OverlayState` settings.. the former is preferable, as you can then easily switch z-indexes with media queries.
Beitragsleitfaden
Rechercherichtung
Beginne damit, die Overlay-Implementierung und die Elemente namens md-overlay-container, md-overlay-pane, md-menu-click-catcher und OverlayState zu lokalisieren. Reproduziere das verlinkte Stacking-Problem von md-menu und ermittle anschließend, wie die manuelle Steuerung des z-index des Panes und das Entfernen des z-index des Containers funktionieren sollten, ohne von Benutzern erstellte oder Angular-Komponenten-Overlays zu beeinträchtigen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- frontend
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100