W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2008

html5/spec Overview.html,1.974,1.975

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 18 Jun 2008 04:30:21 +0000
To: public-html-commits@w3.org
Message-Id: <E1K8pJO-0000Tn-1v@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv1805

Modified Files:
	Overview.html 
Log Message:
Allow sniffing when the expected type is an image. (continuation of changes for previous checkin) (whatwg r1785)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.974
retrieving revision 1.975
diff -u -d -r1.974 -r1.975
--- Overview.html	18 Jun 2008 04:26:07 -0000	1.974
+++ Overview.html	18 Jun 2008 04:30:19 -0000	1.975
@@ -7813,18 +7813,19 @@
    whether to <em>apply</em> the resource, not the aforementioned assumed
    type.
 
-  <p>If the resource is expected to be an image, user agents may apply the <a
-   href="#content-type6" title="Content-Type sniffing: image">image sniffing
-   rules</a>, with the <var title="">official type</var> being the type
-   determined from the resource's <a href="#content-type8"
-   title=Content-Type>Content-Type metadata</a>, and use the resulting
-   sniffed type of the resource as if it was the actual type. Otherwise, if
-   the resource is not expected to be an image, or if the user agent opts not
-   to apply those rules, then the user agent must use the resource's <a
-   href="#content-type8" title=Content-Type>Content-Type metadata</a> to
-   determine the type of the resource. If there is no type metadata, but the
-   external resource link type has a default type defined, then the user
-   agent must assume that the resource is of that type.
+  <p id=concept-link-type-sniffing>If the resource is expected to be an
+   image, user agents may apply the <a href="#content-type6"
+   title="Content-Type sniffing: image">image sniffing rules</a>, with the
+   <var title="">official type</var> being the type determined from the
+   resource's <a href="#content-type8" title=Content-Type>Content-Type
+   metadata</a>, and use the resulting sniffed type of the resource as if it
+   was the actual type. Otherwise, if the resource is not expected to be an
+   image, or if the user agent opts not to apply those rules, then the user
+   agent must use the resource's <a href="#content-type8"
+   title=Content-Type>Content-Type metadata</a> to determine the type of the
+   resource. If there is no type metadata, but the external resource link
+   type has a default type defined, then the user agent must assume that the
+   resource is of that type.
 
   <p>Once the user agent has established the type of the resource, the user
    agent must apply the resource if it is of a supported type and the other
@@ -36529,9 +36530,9 @@
    attributes.
 
   <p>There is no default type for resources given by the <code
-   title=rel-icon><a href="#icon3">icon</a></code> keyword.</p>
-  <!-- XXX we don't define
-  the content-type sniffing for this keyword -->
+   title=rel-icon><a href="#icon3">icon</a></code> keyword. However, for the
+   purposes of <a href="#concept-link-type-sniffing">determining the type of
+   the resource</a>, user agents must expect the resource to be an image.
 
   <p>The <dfn id=sizes0 title=attr-link-sizes><code>sizes</code></dfn>
    attribute gives the sizes of icons for visual media.
Received on Wednesday, 18 June 2008 04:30:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 20:32:57 GMT