Hi Constance! > I like client-side scripts for optional stuff (e.g. validation code that > will be repeated on the server or changing a button's image on mouseover), > but I hate to rely on client-side scripts when people can (and some > paranoid people do) turn it off in the browser.
Some types of things that people commonly do, such as providing treeview navigation tools, are inefficent when a roundtrip is required for each action. And then - unless there's something I don't know, likely since I'm not really a website designer - the back button takes you back through navigations which is really undesirable. Are you aware of techniques to detect when a client has scripting enable and adapt in the cases where it is not? Take the treeview scenario as a sample problem. Zane You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
