-
Notifications
You must be signed in to change notification settings - Fork 208
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
Calendar popup trapped inside container (cutoff) #57
Comments
Hi, if you think only this relative position is the trouble you could make a PR, I will merge it. |
I cannot remove the relative position because the calendar uses position absolute and this is needed. Are you sure this is not on your side - may be some overflow: hidden. |
This is a problem for me as well. Other libraries attach to a node somewhere else to the dom rather than the parent. Using popperjs or something like that, this can be achieved. Would this be welcomed in a pull request @nkostadinov ? |
I try very hard to keep my dependencies to minimum. I would welcome non dependent PR :) . I dont even use a date/time library. I may try to attach the dropdown to another element though - may be an option would suffice. |
@nkostadinov buefy has a
And they update the position once activated using the |
vue-select has an interesting approach. Like buefy, it has an append-to-body prop. However, vue-select makes no attempt to actually position the "dropdown". Rather, it accepts a calculate-position function as a prop for library users to implement the positioning (eg. with Popper.js). |
@bohnman that's an interesting approach. I'll take a look into it. |
A pretty common use case would be to have a container or widget of some sort that has the form inside it. Unfortunately, the calendar popup doesn't popup all the way like it should, as seen below.
This actually can't be fixed by adding style because it's part of the scoped style (which becomes inline). Position relative is the source of the trouble in DateRangePicker.vue.
If you'd like I can try to fix this and send a PR.
The text was updated successfully, but these errors were encountered: