ability to manually control overlay's z-index
- Lenguaje dominante
- TypeScript
- Estrellas
- 25k
- Forks
- 6.8k
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 91
Descripción
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.
Guía de contribución
Línea de trabajo
Comienza localizando la implementación de overlay y los elementos llamados md-overlay-container, md-overlay-pane, md-menu-click-catcher y OverlayState. Reproduce el problema de stacking de md-menu enlazado y determina después cómo deberían funcionar el control manual del z-index del pane y la eliminación del z-index del contenedor sin romper los overlays creados por el usuario o por componentes de Angular.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, typescript
- Área
- frontend
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100