-
Notifications
You must be signed in to change notification settings - Fork 504
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
Problem when navbar is collapsed #144
Comments
Sorry, was a little imprecise. By "within a navbar that is collapsed", I meant: Within a navbar that has been opened as a "stacked list as result of clicking on the button that has replaced the navbar because the window is narrow enough to trigger the navbar collapse. Ex. code: Test case
|
Update: Note that this is only a problem for non-touch screens where hover is possible, but browser window is nevertheless narrow enough to trigger a collapse of the navbar.
|
I've had the same problem. I have also fixed it on my side by checking if To handle cases such as someone resizing their browser it would be nice to have some way to disable dropdownHover again once it has been enabled, such as |
me too, and since an image (ops... a code!) is worth a thousand words, here is a fiddle that shows the problem: http://www.codeply.com/go/GQsnKuiNXB Select the smartphone viewport width (smartphone icon bottom right), open the dropdown menu and then go to "About" or "Contact" item: the dropdown disappears |
In dropdown menus within a navbar that is collapsed for which data-hover=dropdown, when I click on the dropdown menu it drops down ok, but then when I move cursor over the "dropdowned" menu, it disappears within the data-delay timeout. I think what is happening is that it detects that the cursor has moved out of the triggering dropdown (and when the cursor is over the dropdowned menu it is also happens to hover over another "top level" menu item), so it collapses its child. But it should not collapse it in this case, because the cursor is over a child. Happens whether or not data-close-others="false"
The text was updated successfully, but these errors were encountered: