-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
ngbDropdown closes when scrollbars are used #3063
Comments
Hey, @kaiza, as a workaround I'd suggest for this case you use Needs investigation though, in bootstrap it closes when you click in |
Thanks @maxokorokov - I already figured out that workaround but the default behaviour definitely doesn't seem right. |
Is there a nightly version of the library, or a timeframe for the 4.1.3 release? We're finding this to be a surprisingly severe pain point (users fixate on these things far too much), and I'm looking forward to closing this out in our bug list. Thanks! |
@alignsoft just released, many holidays in May. Let us know if anything is still not working! |
Fixed - thanks for the swift response - very much appreciated! |
I am facing the same issue. I am using "@ng-bootstrap/ng-bootstrap": "^5.1.1", "Angular version": "8.2.8". I tried using autoClose="outside", but the dropdown doesn't close after selection. We need to manually close it. |
@hinalshah91 the use case in question works fine with Angular 8.1 and ng-bootstrap 5.1.1 → ex. https://stackblitz.com/edit/angular-khpeym-wepb7j?file=app/app.component.ts Commenting on closed issues is usually not helpful, I've seen this one by change. Open a new one with the minimal reproduction scenario if you have any issues. |
Bug description:
If you have an ngbDropdownMenu with a scrollbar and you click on the scrollbar or drag it, the dropdown closes.
Link to minimally-working StackBlitz that reproduces the issue:
https://stackblitz.com/edit/angular-khpeym
Versions of Angular, ng-bootstrap and Bootstrap:
Angular: 7.2.5
ng-bootstrap: 4.0.4 but also tried 4.1.0
Bootstrap: 4.3.1
The text was updated successfully, but these errors were encountered: