> I changed my mind. I just read this article and I don't find it useful. > I think it lacks in-depth knowledge or he simply didn't took the best > approach for this topic.
As you obviously know the better approach, why not write a better article? Actually,simply naming the approach would be helpful. Judging is easy, especially when you make assumptions. Here is the assumption this article made: a drop down menu should work regardless of input device and stay on the screen when completely expanded without causing scrollbars and thus becoming impossible to reach the last items. Anything wrong with that? > I don't think he's wrong (solely in the point that hybrid menus are > better), but anyone with some knowledge could think of this article as > poorly-done or not being objective --he seems to be some sort of JS expert. What is the knowledge you talk about here that would make people think of this article as poorly done or not objective? The fact/assumption of "he" being a JavaScript expert would also mean that the the CSS menus in Eric Meyer's books also by default are a bad solution and the chapter not objective and bad, wouldn't it? Who should write an objective article? A brick layer? Or maybe an interaction designer? > The way he uses to expose his point of view looks more like saying CSS is > plain wrong, it also shows a lack of understanding of it and seems to > believe there's no common sense (which could easily be applied to both CSS > and JS). Again, please enlight us as to the lack of understanding of CSS and especially the lack of common sense. Also, point out where the article says CSS is plain wrong. There are parts that say that using CSS for *these solutions* is wrong, and there are arguments why but where is the sweeping statement? These are rather tough accusations you make here, however they lack the proof. Let's see an application of common sense and find a CSS only menu that works with a keyboard and stays on-screen even if there is not enough space for it to show more to the left or the bottom. > Anyway, it's good to have it as a reference, but I do believe people > should investigate a little more. I think people should stop trying to prove a point in one direction or another but use what works reliably. Point is that with CSS you make assumptions, with CSS and JS you can test before you apply (is there enough space? Would a delay in showing or hiding a menu make it more usable?) Maybe the question is "what should a drop down menu achieve and what are the circumstances it could be used" and then we decide the technology to apply. Right now all of the discussions on this matter start with "I want to use technology XYZ as I know it and it IS the best for this!". All other technologies are black magic and insecure and probably steal your firstborn when you don't watch them closely. ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
