Re: Menu stuff (just to annoy the devs)
Reply #18 –
Come to think of it, the best solution, if anyone wants to keep a hover menu option, would probably be to ditch javascript entirely and just rely on CSS3. With XP being dead and buried next month, IE8 usage will probably decline significantly and almost immediately. That means any browsers worth worrying about will be able to do mouseout delays and whatever without any js at all.
Question: what does Elk do about tablets? I know you have the smartphone icon-based menu for small screens, but what about tablets with large res? Do they automatically go to a click menu or do they currently default to the hover menu?
ETA: Seems to me the current system is plumbers crack about in a way. It developed piecemeal from the CSS2-only SMF 2.0.x drop menu system, with more and more stuff added on as time went.
Given that things are supposedly touchscreen-first these days, which really requires click menus, and given that some very sane and intelligent people (not mentioning any names or projects) actually prefer click menus even with mouse and desktop, as far as I can tell the best way of dealing with it would be to make click menus the default. Naturally these would have full CSS fallback in case js was disabled for any reason, which means that if anyone does want to keep a hover menu option, all it would have to do is disable the js on the menus.
Re: Menu stuff (just to annoy the devs)
Reply #19 –
I replaced all of my painfully written js from menubvode a few weeks ago, and it felt liberating. There's so little you can do in js that css3 can't do with transition tricks!
Re: Menu stuff (just to annoy the devs)
Reply #20 –
Menu code, not menubvode. Damn spell checker not doing its job...
Re: Menu stuff (just to annoy the devs)
Reply #21 –
Yeah but CSS3 is only good for hover drops. Still need some js for click drops.