- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 01 May 2009 23:15:52 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv575 Modified Files: Overview.html Log Message: I keep forgetting the text/css quirk is already defined, so let's link to it explicitly. (whatwg r3057) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2216 retrieving revision 1.2217 diff -u -d -r1.2216 -r1.2217 --- Overview.html 1 May 2009 06:22:07 -0000 1.2216 +++ Overview.html 1 May 2009 23:15:49 -0000 1.2217 @@ -9054,18 +9054,23 @@ used to determine whether to <em>apply</em> the resource, not the aforementioned assumed type.</p> - <p id="concept-link-type-sniffing">If the resource is expected to be - an image, user agents may apply the <a href="#content-type-sniffing:-image" 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-type-0" 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-type-0" title="Content-Type">Content-Type metadata</a> to determine the + <p id="concept-link-type-sniffing">If the external resource link + type defines rules for processing the resource's <a href="#content-type-0" title="Content-Type">Content-Type metadata</a>, then those rules + apply. Otherwise, if the resource is expected to be an image, user + agents may apply the <a href="#content-type-sniffing:-image" 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-type-0" 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 neither of these conditions apply or if the user + agent opts not to apply the image sniffing rules, then the user + agent must use the resource's <a href="#content-type-0" 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> + <p class="note">The <code title="link-type-stylesheet">stylesheet</code> link type defines + rules for processing the resource's <a href="#content-type-0" title="Content-Type">Content-Type metadata</a>.</p> + <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 relevant conditions apply, and must ignore the resource
Received on Friday, 1 May 2009 23:16:01 UTC