-
Notifications
You must be signed in to change notification settings - Fork 314
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
Remove useClick feature? #47
Comments
Hi, I'm using your plugin on a number of sites and never used the click-feature, the recent improvements for touch-devices makes the click-feature even more redundant for me... Long story short: I'm all for removing this... ;) Best regards, |
Thanks for chiming in. Music to my ears! |
The unruly nature of the onclick is the reason I have not upgraded to the latest version .. and as you noted trying to support both and touch devices is causing some bloat and development pain. I'd be fine seeing it removed and done as a separate plug-in for those folks that prefer click over hover (I let them choose since it was less work than arguing with em!) |
I'm in favor of this as long as touch is supported. |
I've found that even with the hoverIntent plugin people still find clicking easier than hovering especially on laptops. There are a few UX articles floating around about the caveats of the hover interaction. If you can bare it, I wouldn't remove it. I do think moving it to a separate plugin would be fine though. |
Thanks very much for the feedback. |
Know this is closed, but would be great to see this at least moved to a separate plugin, the click was one of my main reasons for my excitement in seeing superfish brought back into active development. |
Removing |
Okay, so I've created Superclick. I'll get it up on GitHub in the next day or so. |
Here is the Superclick repo. |
nice. |
One downside of hover is with a non-touch device that has a small viewport, it's tricky to navigate a mobile-optimized menu with hovers. You have to be really precise with the pointer and things open/close like wild. |
Hi, When the mobile-menu appears I would like to be able to navigate to a node point. At the moment the menu is constructed in a way that clicking on the first level (node) only the submenu opens. Would it be possible to modify the code such that with a click on the left side the node's URL opens Thanks for helping. Christoph |
Hello, Sorry, that site doesn't use Superfish. |
Oh, sorry. Just thought because it was using class names like sf-sub-indicator and other class names starting with sf-. And, last not least, since it contains (in functions.js)
Just make the browser window smaller. Then the hamburger menu will appear. Isn't that SF? |
I'm regretting adding the
useClick
feature as it increases the complexity of the code and eats up development time that I'd prefer to spend focussing on hover events (plus touch and keyboard support, of course), which is truer to the mission of Superfish.I think it would be a better idea to have a separate click menu plugin, allowing me to remove some complexity and bloat from Superfish and making room for further enhancements. I'm not seeing much benefit of having both click and hover capability in the one plugin, and the amount of
if (o.useClick) {…
forks that keep needing to be added is telling.I'd really appreciate hearing some opinions on this.
The text was updated successfully, but these errors were encountered: