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

[whatwg] Status bars and progress indicators

From: Afternoon <afternoon@uk2.net>
Date: Tue, 21 Sep 2004 03:23:37 +0100
Message-ID: <3EB6B46D-0B75-11D9-AD68-000A957E8988@uk2.net>


>   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!

In an application that uses multiple windows (yes, multiple windows are 
a good thing sometimes), many of these UA features are duplicated. They 
do nothing but eat up valuable real estate. While it is fair to say 
that the developer wants his/her application to be visually clean, it 
is also in the user's interest for the interface to be straightforward 
and not to add confusion by duplicating controls.

In addition, the functions performed by certain controls may be totally 
inappropriate to the current application stage, for example the refresh 
control becomes a dangerous liability just after a user has submitted 
their credit card details and placed an order.

An application should have the flexibility to provide users with the 
controls they need to operate that application, no more, no less.

Ben


((Ben Godfrey) (Software) (see "http://www.cohack.com/"))
Received on Monday, 20 September 2004 19:23:37 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:20 UTC