-
Notifications
You must be signed in to change notification settings - Fork 230
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
IE9 problem - ghost clickable links stay when menu is closed #19
Comments
BTW - to see the hit zones, just hover your mouse below the minimised menu icon - in the area where the menu normally pops up. In IE, the pointer icon will change to the finger, and the destination URL will appear in your browser's status bar. |
The problem seems to be the CSS-property "pointer-events", it works only in IE11+, not in IE 6-10: To fix that problem i add
but this breaks some animations.. |
+1 Just noticed the same problem on IE9 However thanks for the tip. When you say animations are broken, do you mean on all browsers when adding those rules ? |
We don't use this lib anymore, prefering now http://slicknav.com/ . But i think yes, with the fix above, animations on all browsers are broken. You could try to add that css only for IE < 11. |
To avoid taking the risk, I managed so those rules are applied only to IE9 and below using browser detection. |
When viewing pages with dlmenu using IE9...
Problem appears in my project as well as on the demo pages for dlmenu.
Expected behaviour:
When menu is minimised (closed), normally the area where the menu expands is completely clear. Hit zones for the menu items are hidden. This can be seen in Firefox, Safari, etc.
IE9 behaviour:
When the menu is minimised (closed), a ghost area remains where the menu would normally expand to, when open. Menu content seems invisible, however the hit zones for menu items remain present and active.
These hit zones overlay the content of the page, including any links or other things in the content, which presents as a bug to users.
Can anything be done to avoid this issue in IE9?
The text was updated successfully, but these errors were encountered: