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
While below is our site configuration, I have explicitly disabled the portion of the code that causes this issue as a stopgap solution. But this is reproducible even on the documentation site, so I find that a non-issue (and I don't know how the doc site is built, so I can't fill it out for that.)
Hosted on GitHub Pages (if yes provide URL to site): yes, but it doesn't use GitHub Pages' build engine, rather our own Actions script that uses updated Jekyll: https://3ds.hacks.guide
Operating system: All
Expected behavior
Upon timeout of the navigation dropdown, the page should un-fade, and be visible as usual.
Actual behaviour
This behaviour is reproducible on the documentation site as well.
In the event that one opens the navigation bar dropdown menu, let the mouse leave, and wait for the timeout as specified in the greedy navigation JavaScript, the dropdown will disappear as expected, but the background fade will not.
Clicking anywhere else on the page will remove the fade, but the dropdown menu appears again with no fade, and the behaviour persists this way until letting the menu timeout again.
Steps to reproduce the behavior
Have as many items in the navigation.yml to make the greedy-nav dropdown appear
Click on dropdown
Move mouse away from dropdown and wait a few seconds (triggers mouseleave)
The issue starts here, where the dropdown disappears, but the background still has translucency, and the dropdown toggle still shows an X
Click anywhere on the screen
This will remove the translucency, and the X will turn back into hamburger menu, but then the dropdown menu appears again...?
Click on the dropdown again
This adds translucency again, and the hamburger menu changes to an X, but the dropdown menu disappears
Click anywhere on the screen to go back to step 3
Move the mouse into the dropdown menu, then move it back out, to return to a normal state
Other
No response
The text was updated successfully, but these errors were encountered:
What happened?
While below is our site configuration, I have explicitly disabled the portion of the code that causes this issue as a stopgap solution. But this is reproducible even on the documentation site, so I find that a non-issue (and I don't know how the doc site is built, so I can't fill it out for that.)
Expected behavior
Upon timeout of the navigation dropdown, the page should un-fade, and be visible as usual.
Actual behaviour
This behaviour is reproducible on the documentation site as well.
In the event that one opens the navigation bar dropdown menu, let the mouse leave, and wait for the timeout as specified in the greedy navigation JavaScript, the dropdown will disappear as expected, but the background fade will not.
Clicking anywhere else on the page will remove the fade, but the dropdown menu appears again with no fade, and the behaviour persists this way until letting the menu timeout again.
Steps to reproduce the behavior
Other
No response
The text was updated successfully, but these errors were encountered: