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
If the connected component is narrower than the viewport, the CDK should never position beyond the bounds of the viewport. I can't think of when this would be desirable. The top left corner should be at least 0, and the bottom right corner should be at most the width/height of body.
What is the current behavior?
CDK overlays sometimes gets positioned such that the component attached to the overlay gets cut off.
What is the use-case or motivation for changing an existing behavior?
Users should be able to see the entire overlay if there is room to display it. If the overlays have close buttons, it's possible that they could be inaccessible.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
5.0.0, 5.0.0, chrome
Is there anything else we should know?
The text was updated successfully, but these errors were encountered:
Bug, feature request, or proposal:
Bug
What is the expected behavior?
If the connected component is narrower than the viewport, the CDK should never position beyond the bounds of the viewport. I can't think of when this would be desirable. The top left corner should be at least 0, and the bottom right corner should be at most the width/height of
body
.What is the current behavior?
CDK overlays sometimes gets positioned such that the component attached to the overlay gets cut off.
What are the steps to reproduce?
http://plnkr.co/edit/qbivIGe33PpHY1ybd6ZR?p=preview
Good:

Bad:
What is the use-case or motivation for changing an existing behavior?
Users should be able to see the entire overlay if there is room to display it. If the overlays have close buttons, it's possible that they could be inaccessible.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
5.0.0, 5.0.0, chrome
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: