- From: Web Security Context Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Wed, 3 Oct 2007 17:28:30 +0000 (GMT)
- To: public-wsc-wg@w3.org
ISSUE-116 (Hal): Should users be able to reconfigure primary chrome? [Techniques] http://www.w3.org/2006/WSC/track/issues/ Raised by: Hal Lockhart On product: Techniques As a side issue in the debate over logotypes, Phil implied that users might reconfigure their primary chrome to for example, suppress some of the information. Given the amount of attention we have paid to using primary chrome to display WSC, and the fact that there could be interdependence between distinct indicators, this appears to present some risks. At the very least the doc should make a clear statement of what is allowed or not allowed. I suggest the following. 1. The user agent MUST NOT permit programs to reconfigure the primary chrome via API in such a way as to hide any of the indicators that this document requires be displayed in primary chrome. I can live with either of the following, but slightly prefer 2a. 2a. The user agent MUST NOT permit the user to administratively reconfigure the primary chrome in such a way as to hide any of the indicators that this document requires be displayed in primary chrome. 2b. The initial configuration of the user user agent MUST show all of the indicators that this document requires be displayed in primary chrome. The user agent SHOULD NOT permit the user to administratively reconfigure the primary chrome in such a way as to hide any of these indicators. If the user agent does permit this, it MUST provide a mechanism to easily reset the user agent to display the all the required indicators in primary chrome. Hal
Received on Wednesday, 3 October 2007 17:28:37 UTC