- From: Thomas Roessler <tlr@w3.org>
- Date: Thu, 28 Feb 2008 01:40:43 +0100
- To: Johnathan Nightingale <johnath@mozilla.com>
- Cc: W3C WSC W3C WSC Public <public-wsc-wg@w3.org>
On 2007-12-03 16:57:43 -0500, Johnathan Nightingale wrote: > 1) Changing the normative text in §8.1.2 to read: >> Web User Agents MUST NOT communicate trust information using user interface >> elements which can be mimicked in chrome by web content. Site-controlled >> content (e.g. page title, favicon) MAY be hosted in chrome, but this >> content MUST NOT be displayed in a manner that confuses hosted content and >> chrome indicators. > 2) Removing the MUST NOT bullets in §8.1.3 relating to favicons. We can > offer more guidance here though, so that the new section might read: >> 8.1.3 Techniques >> This section is normative. >> The following technique is neither necessary nor sufficient to claim >> conformance with the Requirement. However, conformance with this technique >> entails conformance with the necessary techniques that concern favorite >> icons. >> >> - Web User Agents MAY ignore favorite icon [FAVICON] references that are >> part of Web content. >> - Web User Agents SHOULD NOT use a 16x16 image in chrome to indicate >> security status if doing so would allow the FAVICON to mimic it. Per ACTION-392, I'm merging this proposal into the editor's draft. In doing so, I'll also drop the Requirements / Techniques structure for 8.1, and also the remarks about facets of the user interface (we seemed to agree on the latter at the face-to-face), i.e., 8.1.1. Relevant minutes: http://www.w3.org/2008/02/06-wsc-minutes.html#item07 I haven't gone through the issues listed in this part of the spec; some might be moot now. Web Security Context: Experience, Indicators, and Trust Editor's Draft 28 February 2008 $Revision: 1.169 $ $Date: 2008/02/28 00:38:51 $ http://www.w3.org/2006/WSC/drafts/rec/rewrite.html#site-identifying Regards, -- Thomas Roessler, W3C <tlr@w3.org>
Received on Thursday, 28 February 2008 00:40:52 UTC