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
Issue scrolling with the select box open #8
Comments
Sorry, i can't reproduce. Kind regards |
I'm using chrome 83.0, linux opensuse 15.1. This was the only way I could find to keep the menu in place:
|
I'll try to reproduce : the plugin should be css proof : I mean it should work in every situation (css collison outise it's normal scope) |
no thanks I need css. I'll do tests when I can |
Does this help? check out the Aid Types field, sorry I can't provide more |
The problems comes from the class .layout-body The positionning of the selectBox which was relative to the body is now relative to this div and the menu fixed see css-position |
It's very interesting : transform in a parent make this element the reference element for a child positionned absolutely
but when I use the top to position the menu content, then the positioning is false because the top is set from another DOM element than the body tag. I have tried to take advantage of the disruption effect of transform by putting it on the menu button itself ! It works perfectly, the menu is perfectly positionned, but when it overlap another menu then the button part of the other menu show thru the menu content ! At this time I can only advice : don't use transform with vanillaSelectBox I will put a big WIP on the work |
Issue scrolling with the select box open #8
OK Roberto, |
Thank you, give me a few days to integrate it into our work and test |
Tried it and confirmed it's working, thanks |
I'm very glad it is fixed |
I noticed in #5 that you mentioned a fix on a scrolling problem, I think it's still happening, I'm using the latest 0.35 version, here's how it looks:
also checked and the .css is the latest, I'm wondering if there's a conflict with any elements in the page that might trigger this behavior.
Good job on this BTW !!!
The text was updated successfully, but these errors were encountered: