I have to agree, mainly because the menu structure is being generated dynamically from the loop so it would be hell to have to insert additional conditional after each line.ogun wrote: would be tempted to go for a straightforward ie conditional statement in the header around the csshover fix rather than taking the cssplay route.
LMAO!ogun wrote: there are still people out there with ancient browsers, but they probably don't have any money so an online shop doesn't need to worry about them too much
Thought about that too, but that might also get tricky to place in a dynamically created menu. Since we need the csshover.htc anyway, might as well add a small little timer scriptogun wrote: for the disappearing menus on mouseout, an invisible area around the menus (e.g. some padding in the containing ULs) would cover most user inaccuracies with the mouse.
Well, I've seen the new menu actually..... its a different javascript platform... but still javascript... and possibly still file-based, tho I can't really tell. It's very nice and robust, but a bit over-the-top IMO. I will reserve any opinions until the its released. But from what I saw, I see myself replacing my local copy with this menu.ogun wrote:..before going much further? maybe Daniel's already removed the js/changed how the menu works.
