ngx-bootstrap
ngx-bootstrap copied to clipboard
Dropdown nested has issue and not to be resolve
From issue #3703 and #3851
It still a bug until latest version (3.0.1)
on #3703 close for duplicate but I don't see other issue related
Fixing it?The next version?
+1
+1. Please fix it, I'm trying to create a workaround but It's still buggy.
hii is there any workarounds for nested dropdowns to not overlap each other on mouseover?
I'm also interested on some workaround for this
The bug is still unsolved. Any workaround for this?
not resolve in 5.2.0
hello everyone,
you can make to work better by changing the trigger of the dropdown menu item form mouseover to mouseclick => triggers="mouseclick"
hello everyone,
you can make to work better by changing the trigger of the dropdown menu item form mouseover to mouseclick => triggers="mouseclick"
Hi, I've tryied this option, but it closes the top menu.
Can you post your code, please?
Thanks!
<div class="btn-group" dropdown [dropup]="true" [insideClick]="true">
U need to enable [insideClick] first, then change 'mouseover' to 'mouseclick'
<li role="menuitem" dropdown [dropup]="true" triggers="mouseclick" placement="right" container="body">
<div class="btn-group" dropdown [dropup]="true" [insideClick]="true">
U need to enable [insideClick] first, then change 'mouseover' to 'mouseclick'<li role="menuitem" dropdown [dropup]="true" triggers="mouseclick" placement="right" container="body">
this works but doesn't close the top menu on inside click of the nested menu.
<div class="btn-group" dropdown [dropup]="true" [insideClick]="true">
U need to enable [insideClick] first, then change 'mouseover' to 'mouseclick'<li role="menuitem" dropdown [dropup]="true" triggers="mouseclick" placement="right" container="body">
this works but doesn't close the top menu on inside click of the nested menu.
That can be resolved by adding a manual toggle to any item of the top menu that is not a submenu trigger. Reference the manual toggle section of the dropdown component documentation. A bit annoying if you have many items (and are not using ngFor), but it at least resolves the issue for now until we get a proper fix.