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
Dropdown menu shouldn't close itself when there is a form inside the dropdown menu and user is interacting with the form. Even with [autoClose]="true" (default)
Link to minimally-working StackBlitz that reproduces the issue:
Stackblitz with both ng-bootstrap and bootstrap dropdowns to compare:
I am interested in working on this. I'm thinking I would create a ngbDropdownIgnore directive to ignore clicks on certain elements. So the user could apply this to the form or whatever other elements they want.
Is this an acceptable approach? If so, would that be considered a new feature instead of a bugfix? If not, would it be better to explicitly ignore form elements only?
maxokorokov
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
May 6, 2019
@maxokorokov I was just scratching my head for a good hour digging into the source code trying to figure out why my code (on v4.1.1) was not working when using the exact same code that is on in the documentation example here. Had to create a fresh Angular app and reproduce the scenario where I then inspected the source code and discovered your fix that was introduced in 4.1.3.
Bug description:
Dropdown menu shouldn't close itself when there is a form inside the dropdown menu and user is interacting with the form. Even with
[autoClose]="true"
(default)Link to minimally-working StackBlitz that reproduces the issue:
Stackblitz with both ng-bootstrap and bootstrap dropdowns to compare:
https://stackblitz.com/edit/angular-uahpzh?file=index.html
To reproduce:
ng-bootstrap
button to open the menuVersions of Angular, ng-bootstrap and Bootstrap:
ng-bootstrap: 4.1.1
The text was updated successfully, but these errors were encountered: