- From: poot <cvsmail@w3.org>
- Date: Sat, 2 May 2009 08:17:27 +0900 (JST)
- To: public-html-diffs@w3.org
I keep forgetting the text/css quirk is already defined, so let's link to it explicitly. (whatwg r3057) type http://people.w3.org/mike/diffs/html5/spec/Overview.1.2217.html#attr-link-type If the external resource link type defines rules for processing the resource's Content-Type metadata, then those rules apply. Otherwise, if the resource is expected to be an image, user agents may apply the image sniffing rules, with the official type being the type determined from the resource's Content-Type metadata, 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 Content-Type metadata 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. http://people.w3.org/mike/diffs/html5/spec/Overview.1.2217.html#concept-link-type-sniffing http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2216&r2=1.2217&f=h http://html5.org/tools/web-apps-tracker?from=3056&to=3057 =================================================================== 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:18:08 UTC