You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the use-case or motivation for changing an existing behavior?
My Component2 equivalent is a layout component which has a header element and a wrapper for a content element which should be rendered only if some condition is true. In this case i want to pass a mat-drawer-container as content.
So basically the use-case is "MatDrawer with content-projection and structural directives".
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.1.3
Material 6.4.6
Tested on Windows with Chrome, Firefox and IE11
The text was updated successfully, but these errors were encountered:
Bug, feature request, or proposal:
Bug
What is the expected behavior?
mat-drawer
withmode=side
andopened=true
should render drawer and content next to each other (side-by-side)What is the current behavior?
The
mat-drawer-content
element "overlays"mat-drawer
and takes full container width under the following conditions:mat-drawer-container
is in template of Component1 and passed as content-child into another component (Component2)ng-content
tag within it's template and theng-content
tag is wrapped into a containerdiv
div
has anngIf
directive which evaluatesfalse
initially and then becomestrue
after some time.What are the steps to reproduce?
Notice how the text inside
mat-drawer-content
is not visible, since it is hidden behindmat-drawer
:https://stackblitz.com/edit/angular-khyg2w
What is the use-case or motivation for changing an existing behavior?
My Component2 equivalent is a layout component which has a header element and a wrapper for a content element which should be rendered only if some condition is true. In this case i want to pass a
mat-drawer-container
as content.So basically the use-case is "MatDrawer with content-projection and structural directives".
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.1.3
Material 6.4.6
Tested on Windows with Chrome, Firefox and IE11
The text was updated successfully, but these errors were encountered: