Re: Menus menyooz munyews - them things with all teh linkys in 'em.
Reply #15 – January 01, 2013, 08:45:18 pm
Oh that. Well I think it's good to have some hover indication of a link's target area. All the other buttons do it, whether they have a drop menu or not. Personal preference, I suppose.
Re: Menus menyooz munyews - them things with all teh linkys in 'em.
Reply #19 – January 06, 2013, 12:15:28 am
Ok, if you want it in plain English: this thing is really good for blind people. Happy now?
Re: Menus menyooz munyews - them things with all teh linkys in 'em.
Reply #26 – January 27, 2013, 05:22:24 pm
No. You can still use the top level link. Right click > open in new tab (or however you like). TBH in testing I was finding that the click menus were not really slower to navigate, much to my surprise. You have to click, but you do not have to wait for hoverIntent or anything else. Net result is more actions but no loss of speed, and the cleaner and simpler code is a bonus that gives smoother rendering/less overhead. Really, you have to try both in intensive use for a week or so to get a good comparison. Having done that, I'm personally sold on click-to-open, but it would be possible to have click or hover selectable as a user option if you really wanted to.
Re: Menus menyooz munyews - them things with all teh linkys in 'em.
Reply #27 – February 01, 2013, 05:27:59 pm
Thought of something else, apart from the click vs hover biz. Generally, it's considered best practice to not have too many buttons in the main menu. This comes back to how many thing humans can easily hold in their awareness at the same time. The figures I've seen often recommend no more than six top level buttons. So, are we going to just stick with the age-old spewing out of more buttons as more features are enabled? In my experience the calendar and memberlist (just to take two random examples) are rarely accessed, but quite useful to have nonetheless. These would be ideal candidates for inclusion in a second level droppy.