W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2004

[whatwg] Status bars and progress indicators

From: Lachlan Hunt <lachlan.hunt@iinet.net.au>
Date: Tue, 21 Sep 2004 12:09:32 +1000
Message-ID: <414F8D5C.5020307@iinet.net.au>
Matthew Raymond wrote:
>    (Personally, I don't understand why they won't let programs turn off 
> the status bar when the user still can. You could simply ask the user to 
> hide the status bar before starting the program. Does Microsoft block 
> detection of whether or not the status bar is hidden, by the way? If so, 
> the application could simply refuse to run unless the user disables the 
> status bar.)

An application *must not* have any control over, or be able to force the 
user into changing the UAs application interface.  If a user wants to 
have a status bar, the web application *must not* be able to alter that 
decision in any way.  In general, a web application *must not* have any 
control over anything outside of the viewport.  If they did, then as a 
user, I would disable any feature that allowed them to do so.  If that 
broke their application, so that it refused to run because of it, then 
it has failed to degrade gracefully, and violates accessibility guidelines.

   The same applies to menus, toolbars, window resizing, context menus, 
etc. which have previously been able to be disabled/removed by 
JavaScript, but thankfully, modern browsers can now prevent authors 
doing that.  Lets not give back these abilities to the author!

-- 
Lachlan Hunt
http://www.lachy.id.au/
Received on Monday, 20 September 2004 19:09:32 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:37 UTC