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
Datepicker: multiple months out of viewport #1358
Comments
I also had this problem. By having two datepickers in a modal, if I experiment with reducing the width of the viewport they end up outside of the modal instead of getting stacked. |
@PEsteves8 How did you do that? |
What's your question? Having a datepicker in a modal? |
@PEsteves8 Ah same issue as me, so u found no fix? to make them responsive? |
Nope. I suppose the code has to be edited. |
Yeah, currently months are simply displayed horizontally like this without responsiveness: <datepicker>
<div class="months" style="display: flex">
<div class="month" />
<div class="month" />
...
</div>
</datepicker> |
@maxokorokov do you know a way to make them responsive, atleast not go out of the viewport? |
This is duplicate of #1257 |
any progress on this? |
This is neither a duplicate nor is it fixed. The other issue is about wrong placement of the popup. :host ::ng-deep .ngb-dp-months {
flex-flow: row wrap;
justify-content: flex-start;
}
:host ::ng-deep .ngb-dp-month {
flex: 1 0 auto;
} I think this should be the default style, maybe with modifications. Please reopen this issue :) P.S. I can make a pull request if you think this is a reasonable default. |
Bug description:
Cannot make it work well in a grid system, so for example if i have 1
row
and every datepicker is acol-md-4
and I setdisplayMonths
to 6. my idea was that there where blocks like:x. x. x.
x. x. x.
Now when i put 6 datepicker's they are just in 1 line totally out of the viewport! It doesn't matter if there is a row arround it or a container or something similar.
Version of Angular, ng-bootstrap, and Bootstrap:
Angular: 2.3.5
ng-bootstrap:
20
Bootstrap:
6
The text was updated successfully, but these errors were encountered: