Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: phranque
Do you guys have a rule of thumb for this?
I'm sure Brett will pop on this thread tonight or tomorrow. He has a lot of experience in the ag arena.
I'm curious about why you see such a big difference.
I was just at a site (law.com [law.com]) that denied access based on agent name. I switched agent names and walked right in no problems at all. They just lost a potential longterm user and created a vocal critic at the same time - all because of a clueless webmaster.
Don't trust general browser charts since everyone is running with IE as an agent name these days. Most third party browsers, proxy agents, and web kid filters are being delivered with IE agent name as the default.
I think the line is right there on navigation. As long as you do things with jscript that aren't specific to navigation, you'll be alright. Once you start messing with jscript as a form of navigation, that's when the site breaks down.
>I'm curious about why you see such a big difference.
It's not so much that I see a difference, I view BOTH css and js as violations of the KISS principle in most instances. BUT, while I can replicate most of the desired effects of css with tag attributes, there are some instances where js actually simplifies navigation for the vast majority of the users without taxing the CPU with dynamic calls. Here's a frame from a site [stateguide.com] that is the best example. (Sorry for the url-drop, I couldn't think of a way to explain it in under 500 words.)
Basically, I write to NS3 with js 1.2 for navigation. I figure my traffic losses are 8 percent.
When categories are in sight on the page, as in regular HTML nav, they are at least registering in peripheral vision. My feeling is this makes the site stickier. Drop down choices seem a bit "out of sight, out of mind".
Wonder if you have any comments or experience/counter-experience in this area.
In the military base example above, the categories are usually already known to those coming to the page --they are also very limited in number. The js drop-down is really structured to logically replace a simple database sort query. IMO, this was a perfect place to use this type of navigation, but I wouldn't use it for general navigation. In fact, when I use js to write general navigation now, the look harkens back to the old mosaic-style text link panels, I'm just using document.write to do it.