- From: Mike Beltzner <beltzner@mozilla.com>
- Date: Tue, 6 Mar 2007 01:05:37 -0500
- To: Mary Ellen Zurko <Mary_Ellen_Zurko@notesdev.ibm.com>
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 Tuesday, 6 March 2007 06:25:35 UTC