how to make full screen when using inner component.
See original GitHub issueDunno is this question has a weight , but
how to make full screen when using inner component. In may app situation is like
AppModule
Sub Module router outlet is here that restricting
MainComponent
Gallery Component ngx-gallery is in this component view
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How to show a component to full screen? - angular
And set position: absolute . Then to use: <app-component-fullpage *ngIf="clickeed"></app-component-fullpage>.
Read more >CSS Make A Div Height Full Screen [THREE SIMPLE WAYS]
Learn the three QUIKEST ways to make a div full screen using pure CSS that are height:100%, height:100vh and position:absolute.
Read more >How to enter Full-Screen Mode with JavaScript - YouTube
In this video tutorial I'll be showing you how to use the JavaScript Fullscreen API which will allow your website to enter full...
Read more >fullscreen - CSS-Tricks
The following demo shows how we can control background of the image element in fullscreen mode. Click the button to toggle fullscreen mode...
Read more >How To Create a Full screen Overlay Navigation - W3Schools
Slide in from the side. /* Open when someone clicks on the span element */ · width · "100%" · /* Close when...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, now I understand your problem. I will try to fix it at evening.
I have checked material code and this behaviour is because of class
mat-sidenav-content
which hastransform
property. There are two tickets about this issue in material repository https://github.com/angular/material2/issues/4873 and https://github.com/angular/material2/issues/998At this moment there is one option to fix this behaviour