Ryan Nichols wrote: > The reason you would want to usa a 'popup' is for contextual > information. Usually this is in more of a web application scenario than > a website per-se. So you have to think more broadly in the term of > website than serving documents with content in them (ala 'surfing'). > Contextual information has been used for a looong time in user > interfaces. Just think of the numerous desktop applications you use on a > daily basis and how they use pop-up windows to either prompt for more > data, or provide other useful information.
An interesting perspective, Ryan, but I find your contextual argument to be thoroughly convincing as a reinforcement of my own
If a user wants to maintain their context by opening a new tab/window, they may (as indeed, I almost always do). Forcing a new tab/window provides no choice to the user
I could possibly be swayed to agree with you when we are talking about literal, full web applications. If someone chooses to purchase, or install, a specific web application then I am happy to assume that they have done their research. Hence they would be aware of the application's policy regarding use of popups for certain functions etc
I would not consider a shopping cart on a site to qualify as such a web application. The user on an ecommerce site has not chosen the application or its functionality. They using it merely as a means to an end
The difference between the two being that one allows the user a choice (in purchasing the application) whereas the other does not
Now that we are significantly off into the philosophical waffle of hypothetical scenarios and ethical stances (not necessarily a bad thing), I hope all this is helping John sway his usability team!
Cheers, Lachlan ****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
