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

Re: ACTION-106 Propose clarifying language for 8.2.5

From: Thomas Roessler <tlr@w3.org>
Date: Mon, 2 Apr 2007 21:28:15 +0200
To: "Close, Tyler J." <tyler.close@hp.com>
Cc: Web Security Context WG <public-wsc-wg@w3.org>
Message-ID: <20070402192814.GI4111@raktajino.does-not-exist.org>

On 2007-03-26 18:17:04 -0000, Close, Tyler J. wrote:

> The visited site determines what image to serve as its favicon
> and the browser displays it as provided. I don't see how it can
> be argued that the current text is misleading. I think the
> sentence in question is:

>     "In either case, the choice to display a logo, and what image
>     to use, is at the discretion of the visited web site."

> I'd like to better understand why this edit needs to be applied before
> making the change.

The favicon is largely to anything else that the browser displays on
behalf of the site.  In particular, it can be disabled or moved
elsewhere without breaking interactions.

"at the discretion of the visited web site" suggests a much stronger
obligation on the browser's side to actually display a favicon --
I'd apply that phrase, say, to the display of misleading images as
part of the site's content.

So, I'm +1 to Mike's spin on this.

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








> Thanks,
> Tyler
> 
> > -----Original Message-----
> > From: public-wsc-wg-request@w3.org 
> > [mailto:public-wsc-wg-request@w3.org] On Behalf Of Mike Beltzner
> > Sent: Monday, March 05, 2007 10:06 PM
> > To: Mary Ellen Zurko
> > Subject: ACTION-106 Propose clarifying language for 8.2.5 
> > 
> > 
> > ACTION-106
> > 
> > When taken, this action referred to s8.2.5 which has now become
> > s9.2.5 in the latest draft, titled "Poorly defined role for chrome:  
> > Favicon". The issue is around misleading text which implies 
> > that the choice to display a logo and content of that logo is 
> > at the sole discretion of the visited web site, which is untrue.
> > 
> > Section 9.2.5 (http://www.w3.org/TR/wsc-usecases/#favicon) 
> > should be changed to read:
> > 
> > -------------------
> > 
> > 9.2.5 Favicon
> > 
> > Websites can specify a small graphic called a [favicon] to 
> > act as an icon that appears in the URL bar in most desktop 
> > web browsers and on the tabs in some browsers. While the 
> > desktop web browsers control this chrome, none place any 
> > restrictions on the type of websites or type of images that 
> > will be displayed.
> > 
> > As a result, a website can choose to display a favicon that 
> > looks exactly like the padlock icon that is displayed in the 
> > URL bar by many browsers to indicate an SSL connection. In 
> > this case the user may believe that SSL is being used, when it is not.
> > 
> > -------------------
> > 
> > This closes ACTION-106
> > 
> > cheers,
> > mike
> > 
> > 
> 
> 
Received on Monday, 2 April 2007 19:27:51 GMT

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