W3C home > Mailing lists > Public > public-wsc-wg@w3.org > May 2007

Strawman favicon proposal from this morning

From: Thomas Roessler <tlr@w3.org>
Date: Wed, 30 May 2007 13:12:29 +0100
To: WSC WG <public-wsc-wg@w3.org>
Message-ID: <20070530121229.GA32596@raktajino.does-not-exist.org>

I'm including the favicon strawman proposal from this morning below.

The purpose is to illustrate what kinds of elements should be really
part of the structure of requirements eventually suggested, in line
with the proposal I made at [1].

1. http://lists.w3.org/Archives/Public/public-wsc-wg/2007May/0165.html

Elements marked with an asterisk (*) would be the bare minimum we'd
aim at for an FPWD.

Cheers,
-- 
Thomas Roessler, W3C  <tlr@w3.org>




(*) Title

Goals

Overview

(*) Applicable to Implementations

	User agent with ability to display bitmap graphics.

(*) Requirement

	Implementations must not display bitmaps from
	[ unverified | unauthenticated ] sources [ near places
	that are designated for trust indicators ].
	
	[ Verified | authenticated ] sources are defined as ...
	
	[ Places that are designated for display of trust
	indicators ] are defined as ...
	
(*) Techniques

	* favicons are not displayed as part the location bar
	* favicons are not displayed along with certificate 
	  information
	* favicons are not displayed within 10cm of a security
	  indicator
	* ...

Dependencies

Examples (informational)

	Conforming implementation: 
	* LocationBar^2

	Non-conforming implementation:
	* Current web browsers that display the favicon as part
	  of the location bar.

Use-cases (informational)

Attack resistance / limitations

Usability effect

	* expected user behavior
	
	* disruption 


Background (informational)

        ....
Received on Wednesday, 30 May 2007 12:12:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 5 February 2008 03:52:47 GMT