-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MdDialog does not apply width correctly #4620
Comments
dup #3239 |
@ocarreterom Well, the odd thing is, this issue was not present before. I remember running into that duplicate issue back in Feb for something else I was working on, but the width of 815px in my dialogs displayed correctly until the most recent upgrade. This bug is different because my max-width is not reached or exceeded. My max-width for .mat-dialog-container in my application is 95vw, and the dialog is only 815px wide on a full-screen browser. |
Closing issue- looks like I had a bad global CSS property on cdk-overlay-pane that didn't affect things before. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Since upgrading from beta.3 to beta.5, mddialog no longer supports the width property properly. The cdk-overlay-container gets the applied width, but the dialog itself does not.
What is the expected behavior?
The dialog should have the width passed to its configurations
What is the current behavior?
The cdk-overlay-container has the width, throwing off positioning of the dialog
What are the steps to reproduce?
I've applied a width of 815px to the example dialog:
https://plnkr.co/edit/qYMFWtkiu9RnCTEPqTXi?p=preview
What is the use-case or motivation for changing an existing behavior?
To be consistent with how the dialog displayed in beta.3
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.0.2, Material2 2.0.0-beta.5, typescript 2.2.2, Windows 7, Chrome
The text was updated successfully, but these errors were encountered: