bug/feature(sidenav) limited customization caused by 'mat-drawer-inner-container' element
- Lenguaje dominante
- TypeScript
- Estrellas
- 25k
- Forks
- 6.8k
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 91
Descripción
#### Bug, feature request, or proposal:
Bug or feature request
#### What is the expected behavior?
Sidenav to be fully customizable as it was before
#### What is the current behavior?
Having inserted a not-stylable container div between `mat-drawer` and the actual content, I cannot manage height and scrolling as before.
#### What is the use-case or motivation for changing an existing behavior?
For example, in my case I have a 'collapser' button inside sidenav (toggle between normal and drawer mini mode) which must stick to the top while allowing other options to scroll.
```html
...
```
This worked well without the intermediate div, because I could use `display: flex` to manage the height and scrolling making the `links-container` to take all available height minus that taken by the collapser element.
```scss
.mat-sidenav {
display: flex;
flex-direction: column;
}
```
Now I can't do it anymore and I'm forced to use global CSS to put the very same rules on the `mat-drawer-inner-container`, because I cannot style it from inside the component because of CSS scoping.
#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 7
Material 7
#### Is there anything else we should know?
The added element is documented here
https://github.com/angular/material2/blob/76044e8b5c3a6342b05d2e89dfb3b4ccf308c422/src/lib/sidenav/drawer.scss#L162-L167
Guía de contribución
Línea de trabajo
Empieza leyendo las reglas documentadas de mat-drawer-inner-container en src/lib/sidenav/drawer.scss; después, inspecciona cómo afecta el contenedor intermedio al layout de mat-sidenav y a los estilos con alcance de componente. El trabajo estará terminado cuando sidenav pueda admitir el layout de collapser-and-scroll descrito en el issue sin requerir CSS global; no se menciona ningún archivo de pruebas, así que identifica la cobertura relevante de sidenav antes de cambiar el comportamiento.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, scss, typescript
- Área
- frontend
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100