Christian Heilmann wrote: > These are not new things. This is a dead horse that has been flogged > so many times there is nothing left of it. Search CSS-D for "problems > with suckerfish", check cssplay.co.uk, there is nothing whatsoever > creative or inventive about CSS-only menus. It is an endless circle > the CSS Design community has been in ever since Eric Meyer pushed that > envelope back in ... was it 2001?
I believe this article: http://tjkdesign.com/articles/css%20pop%20ups/default.asp is from this "era". So you see that this is not new to me... > presentational technology working together. Please stop giving new > developers ideas that all they will ever need to know is HTML and CSS, > it just is not enough. 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... >>> CSS behaviour is a one trick pony - everything works with pseudo >>> selectors and those don't get applied cross-browser. In order to >>> offer keyboard support you even have to resort to nesting things >>> inside links which simply does not make sense semantically. >> What do you mean? I'm not nesting things inside links. >> The links do not contain anything else than *text*, I'm not even >> using attributes (besides "href" of course)... > 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? ;-) Anyway, it was not an exercice about keyboard naviagation, it was to make sure users do not tab through sub menu items that are *-9999px* to the left of the viewport. BTW, what about my question about me "resorting on nesting things inside links"? ;-) > 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 ;) --- Regards, Thierry | www.TJKDesign.com ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
