> The important principle here is "Web Application != Web > Site".
Why? In many cases, it's the same difference. These days, web "sites" usually are web "applications" on the back-end. There are a lot of stupid users out there. In many cases, every attempt needs to be made to cater to them. > If your users feel compelled to use bookmarks and the back button in > your webapps, despite efforts to train them correctly, this is a pretty > good sign that you have not provided enough suitable navigation > controls in your basic UI. On the contrary, I'd say that if your web application can't handle the back button and bookmarking, then you've designed it incorrectly. ESPECIALLY if your users want to use them :) When web "applications" are done right, they have nice URL's, the back button can be used without causing any problems, and bookmarking is possible wherever it makes sense. IMO, there are too many lazy developers out there who do poor design and don't consider the 'Back' button, for example, then look for cheap hacks to stop the user from using it. Instead, they should think differently and handle these cases. It's sometimes more work, sure, but that's part of the job! Matt
