W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 1998

Re: Spawned browsers, one more time

From: Charles McCathieNevile <charlesn@sunrise.srl.rmit.edu.au>
Date: Sun, 18 Oct 1998 22:09:36 +1000 (EST)
To: WAI UA group <w3c-wai-ua@w3.org>
Message-ID: <Pine.SUN.3.91.981018215845.1329E-100000@sunrise>
proposal to give the user power over browser windows P1. Yes, absolutely, 
for the reasons outlined.

Allow the uer to block creation of new windows, analagous to current 
handling of cookies, p2(1?). I think this is a P3. Assuming new windows 
can be handled accessibly anyway, it is not so necessary, just a nice 
thing to do. Techniques  - allow user to specify (time by time, or set a 
default, at the user's option) whether to allow a new window to be 
opened, the new address to be opeened in the current window, or the new 
address ignored (ahhh - goodbye to GeoCities' advertising. followed I 
suppose by GeoCities itself. hmmm)

If the browser supports multiple windows/browsers make it happen 
explicitly. This seems to be something that every other application 
written can happilt do, but which browsers seem to leave to the OS. It 
should be a P1, but I can't think of any group who is going to be comletely 
cut off, although my experience has been that people simply hut down and 
start again after a  little while of this. I guess it is a priority 2 
really - it really would very significantly improve accessibility.

And yes, Opera certainly allows good windowing control, either by mouse 
or keyboard. Alternatively there is the Lynx approach, which also works 
wuite well, although it can make things frustrating. Accessible window 
control would be prefereable to not having any access to the convenience 
provided by a windows metaphor. W3 browser, running under emacs, also 
does this quite well.

Charles McCathieNevile
Received on Sunday, 18 October 1998 08:13:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:21 UTC