angular / angular/components

feat(SnackBar): allow to define a container in which to render the snackbar

Abierto
#7,764 12 comentarios 26 reacciones 0 asignados Ver en GitHub
area: material/snack-bar feature needs: discussion P5
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:
feature request

#### What is the expected behavior?
There should be a setting to define a container in which the snackbar is positioned in.

#### What is the current behavior?
SnackBar is always positioned based on the viewport.

#### What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-ddtruw

#### What is the use-case or motivation for changing an existing behavior?
I have an app with a static main toolbar at the top. When i position the snackbar to "top right" it will be shown above the main toolbar (see stackblitz example). I would like it to be shown at the top right of the container below the main toolbar (".basic-container" in my stackblitz example).

#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
angular 4.4.2
angular-material 2.0.0 - Beta12
Chrome 61.0.3163.100

#### Is there anything else we should know?
MatSnackBarConfig has a viewContainerRef property. At first i thought this would be exactly what i need but when i tried to change it, it didn't seem to do anything. In the documentation of the MatDialog component (which also has a viewContainerRef property) it is stated that this property does not affect the place where it is rendered. I assume the same goes for MatSnackBar.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza con la reproducción enlazada de StackBlitz e inspecciona MatSnackBarConfig.viewContainerRef, comparando su comportamiento con la ubicación solicitada de .basic-container. Se considera terminado cuando una configuración permite que la SnackBar se renderice y posicione dentro del contenedor elegido en lugar de en el viewport.

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
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.