Seven Reasons in avoiding JavaScript Dynamic Navigation.

I’ ve been a fabulous web developer for finished seven years, and in that , time I’ ve been fortunate enough to find several bad ideas walk out fashion, including splash woven screens and unnecessary framesets. Yet, one really bad idea that appear to be hanging around is the installation of JavaScript for dynamic course-plotting menus. This is unhealthy for several reasons – seven of the most extremely obvious of which are down the page:
When navigation is certainly not permanently displayed, it makes moving through the site difficult.
One of the tips to making a site user-friendly is giving visitors a clear indication of where with the site they are right now, have been, and is going to next. Good navigation will provide all these things, but it’ s impossible to carry out using menus which only appear when mouse is over your ex.
It can be hidden by embedded elements, making navigation to most pages impossible.
Most dynamically-displaying navigation goes ostentatious of content which is visible. However some subject matter, like embedded video in addition to Flash animations, will not be hidden via the navigation bar, but stay with top, with the result that the different parts of the navigation will be impossible to arrive at.
It's not guaranteed for work in all browsers.
Certain browsers have stricter implementations connected with JavaScript than others, consequently while your code may possibly work perfectly well around IE, you’ d better then come some serious testing so that it works equally properly in FireFox, Mozilla, Firefox, Opera and other fraction browsers. If your navigation might be broken then so 's your site.
It requires very good motor control and hand-eye co-ordination.
In keeping with most dynamic selection systems, like Windows’ own personal Start menu, getting around it can take practice and some skill that has a mouse. If you have possibly done a usability learn with elderly users you can get that not everyone realises this easy. Windows does get the very first thing right; you can work with it fairly easily using just simply the arrow keys - seldom the case with JavaScript sat nav.
No major site works by using it.
Google, Amazon, Myspace, BBC, MSN, Yahoo!, Hi5, eBay, Wikipedia, Craigslist, IMDB; everyone name them, they don’ t do it.
There are better ways to accomplish exactly the same thing.
One good thing about JavaScript is which a single script file can easily contain the navigation for the complete site. When you replace that file, the whole entire site’ s navigation up-dates. However, this is also possible with any server-side scripting know-how, outputting standard HTML, with none within the drawbacks listed here.
JavaScript are usually easily turned off – then this site is broken!
Since JavaScript powers a number of the things that are most unwelcome from the internet, such as pop-ups and windows that do not close, some people switch it off (it’ s straightforward do by accessing typically the ‘ Security’ tab for Internet Options). In of which case, most dynamic the navigation stops working, and you might find the navigation bar disappears altogether. Statistics from W3Schools show that 10% within the visitors to your site can have JavaScript disabled. Since there’ s no truly great reason to use JavaScript designed for navigation, why even run possibility that your site will likely be unusable by 10% of your respective visitors?