You like it or not, people ask for these types of menus. Mine was over three years old and I thought it was time to work on a new one using what I learned these last years. I don't see anything wrong with that...
Well, you expect people to keep up with your development and come back and upgrade their implementations, as obviously you found flaws in the old one. Are they likely to do that or will the old version still show up in Google and get used? I get mails all the time about old scripts I created and generally tell people not to use them or in extreme cases redirect their location to an explanation page why my solution was great at that time but is not clever to use now (http://www.onlinetools.org/tools/easyletter.php). Web development requirements change constantly and being on the bleeding edge means you bleed. The best example of that is lots of amazingly cool CSS hacks allowing MSIE6 to be a good browser now causing havoc in MSIE7. You can do what you want, but if you offer it and praise its amazing features people believe they can use your solutions without having to care about anything, and this is most of the time just not possible. Just call them beta, development version or "exercise".
> Hooray! And to reach the last option with a keyboard I need to tab > trough ALL options of the menu - very usable that. A real keyboard > navigation for a menu like this would use cursor keys and allow me to > go up down left and right, spatial navigation as Opera implements it. This was a choice. Is it "worst" than using "display:none" for the only purpose of easing tabbing navigation? ;-)
No, you just don't use CSS for this purpose as with a menu with multi levels and lots of links tabbing is just not a usable way of navigating through it. Be consistent - if you want only mouse users to be able to use your menu, test if a mouse is in use and change the menu when and if that is possible.
BTW, what about my question about me "resorting on nesting things inside links"? ;-)
Who claimed that your example does that? I was talking about CSS only solutions in general, where keyboard enabling means nesting markup invalidly in links (http://cssplay.co.uk/menu/more.html)
> There is more to UI than just using web standard technologies, if you > are to mimick rich user interfaces, then also follow their rules. I'd agree but most of the times with this approach, solutions lack browsers support. I know, I'm bad, I still think we should care for ie 5 (Mac and Win). And that - in its own way - is pushing the envelop ;)
Not really, it is keeping outdated technology alive - like trying to connect a DVD player to a 60ies black and white TV set. If older browsers don't support certain functionality, don't offer it to them - another thing you can only do in JavaScript (unless you count conditional comments as an option): http://developer.yahoo.com/yui/articles/gbs/gbs.html ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
