Open $materialDialog on a scrollable page at the end #249
Comments
|
Hey @ovidiubuligan, Could you post a plunkr or jsfiddle reproducing this? The dialog should be appended to the rootElement of the application, which isn't a scrollable container (it's usually the So even if your scrollable container is scrolled to the bottom, a dialog appended to the application's rootElement should still be in the center of the screen (the body isn't scrolled down, only your container is). Again, an example is necessary. It's possible we may have to restrict the max-height and max-width of the body to 100%, since it sounds like the body may be stretching to fit your scroll container inside. |
|
I think that the main problem is that it isn't applied to the root element (body) from what I saw, it was applied as a child of the html element. I was using the bower release (12 days old currently,so not the latest dev source code). .material-dialog-container.active{
/*position:fixed;*/
/*top:200px;*/
/*left:20%;*/
width: 75%;position: fixed;left: 50%;margin: 0 0 0 -37.5%;
}
material-backdrop {
position:fixed;
}
material-dialog{
position:fixed;
top:15%;
left:35%;
}
.material-dialog-container material-dialog .dialog-content{
padding:60px;
}The app is here : http://ovidiubuligan.github.io and the source code is here : https://github.com/ovidiubuligan/ovidiubuligan.github.io/blob/master/main.css |
|
Can you try out the latest version of material without your custom css and see if it still applies? I just pushed something that will make it so bower is updated every commit with a new version. All you need is to Check out the README for more instructions. |
|
I have to wait until I get home to use bower/node ( corporate filtering ,proxyes, etc) I will update this comment after. |
|
Fixed, thanks. |
I have a page which is vertically scrollable, and when the user is at the end of the page and does something ,I want to open a dialog there . The problem is that the dialog is oppened at the top of the page and not visible.
Are there any quick workarounds for this?
The text was updated successfully, but these errors were encountered: