Browse files

[t] (0) Remove conformance requirements for processing profile=''.

git-svn-id: http://svn.whatwg.org/webapps@4986 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent 81c737d commit 4961080226342d615877cde7cf3053cb7c580912 @Hixie Hixie committed Apr 8, 2010
Showing with 18 additions and 83 deletions.
  1. +6 −25 complete.html
  2. +6 −25 index
  3. +6 −33 source
View
31 complete.html
@@ -85343,33 +85343,14 @@ <h4 id=other-elements,-attributes-and-apis><span class=secno>15.3.4 </span>Other
attribute DOMString <a href=#dom-head-profile title=dom-head-profile>profile</a>;
};</pre>
- <p>User agents should ignore the <code title=attr-head-profile><a href=#attr-head-profile>profile</a></code> content attribute on
- <code><a href=#the-head-element-0>head</a></code> elements.</p>
-
- <p>When the attribute would be used as a list of <a href=#url title=URL>URLs</a> identifying metadata profiles, the user
- agent should instead always assume that all known profiles apply to
- all pages, and should therefore apply the conventions of all known
- metadata profiles to the document, ignoring the value of the
- attribute.</p>
-
- <p>When the attribute's value would be handled as a list of <a href=#url title=URL>URLs</a> to be dereferenced, the user agent must use
- the following steps:</p>
-
- <ol><li><p><a href=#split-a-string-on-spaces title="split a string on spaces">Split on
- spaces</a> the value of the <code title=attr-head-profile><a href=#attr-head-profile>profile</a></code> attribute.</li>
-
- <li><p><a href=#resolve-a-url title="resolve a url">Resolve</a> each resulting
- token relative to the <code><a href=#the-head-element-0>head</a></code> element.</li>
-
- <li><p>For each token that is successfully resolved,
- <a href=#fetch>fetch</a> the resulting <a href=#absolute-url>absolute URL</a> and
- apply the appropriate processing.</li> <!-- http-origin privacy
- sensitive -->
-
- </ol><p>The <dfn id=dom-head-profile title=dom-head-profile><code>profile</code></dfn> IDL
+ <p>The <dfn id=dom-head-profile title=dom-head-profile><code>profile</code></dfn> IDL
attribute of the <code><a href=#the-head-element-0>head</a></code> element must <a href=#reflect>reflect</a>
the content attribute of the same name, as if the attribute's value
- was just a string. (In other words, the value is not <a href=#resolve-a-url title="resolve a url">resolved</a> in any way on getting.)</p>
+ was just a string.</p>
+
+ <p class=note>In other words, the value is not <a href=#resolve-a-url title="resolve a url">resolved</a> in any way on getting. This is
+ mentioned explicitly merely because in earlier versions of HTML, the
+ attribute was defined as taking a <a href=#url>URL</a>.</p>
<hr><pre class=idl>[Supplemental]
interface <a href=#htmlhrelement>HTMLHRElement</a> {
View
31 index
@@ -78615,33 +78615,14 @@ interface <a href=#htmlheadelement>HTMLHeadElement</a> {
attribute DOMString <a href=#dom-head-profile title=dom-head-profile>profile</a>;
};</pre>
- <p>User agents should ignore the <code title=attr-head-profile><a href=#attr-head-profile>profile</a></code> content attribute on
- <code><a href=#the-head-element-0>head</a></code> elements.</p>
-
- <p>When the attribute would be used as a list of <a href=#url title=URL>URLs</a> identifying metadata profiles, the user
- agent should instead always assume that all known profiles apply to
- all pages, and should therefore apply the conventions of all known
- metadata profiles to the document, ignoring the value of the
- attribute.</p>
-
- <p>When the attribute's value would be handled as a list of <a href=#url title=URL>URLs</a> to be dereferenced, the user agent must use
- the following steps:</p>
-
- <ol><li><p><a href=#split-a-string-on-spaces title="split a string on spaces">Split on
- spaces</a> the value of the <code title=attr-head-profile><a href=#attr-head-profile>profile</a></code> attribute.</li>
-
- <li><p><a href=#resolve-a-url title="resolve a url">Resolve</a> each resulting
- token relative to the <code><a href=#the-head-element-0>head</a></code> element.</li>
-
- <li><p>For each token that is successfully resolved,
- <a href=#fetch>fetch</a> the resulting <a href=#absolute-url>absolute URL</a> and
- apply the appropriate processing.</li> <!-- http-origin privacy
- sensitive -->
-
- </ol><p>The <dfn id=dom-head-profile title=dom-head-profile><code>profile</code></dfn> IDL
+ <p>The <dfn id=dom-head-profile title=dom-head-profile><code>profile</code></dfn> IDL
attribute of the <code><a href=#the-head-element-0>head</a></code> element must <a href=#reflect>reflect</a>
the content attribute of the same name, as if the attribute's value
- was just a string. (In other words, the value is not <a href=#resolve-a-url title="resolve a url">resolved</a> in any way on getting.)</p>
+ was just a string.</p>
+
+ <p class=note>In other words, the value is not <a href=#resolve-a-url title="resolve a url">resolved</a> in any way on getting. This is
+ mentioned explicitly merely because in earlier versions of HTML, the
+ attribute was defined as taking a <a href=#url>URL</a>.</p>
<hr><pre class=idl>[Supplemental]
interface <a href=#htmlhrelement>HTMLHRElement</a> {
View
39 source
@@ -97234,42 +97234,15 @@ interface <span>HTMLHeadElement</span> {
attribute DOMString <span title="dom-head-profile">profile</span>;
};</pre>
- <p>User agents should ignore the <code
- title="attr-head-profile">profile</code> content attribute on
- <code>head</code> elements.</p>
-
- <p>When the attribute would be used as a list of <span
- title="URL">URLs</span> identifying metadata profiles, the user
- agent should instead always assume that all known profiles apply to
- all pages, and should therefore apply the conventions of all known
- metadata profiles to the document, ignoring the value of the
- attribute.</p>
-
- <p>When the attribute's value would be handled as a list of <span
- title="URL">URLs</span> to be dereferenced, the user agent must use
- the following steps:</p>
-
- <ol>
-
- <li><p><span title="split a string on spaces">Split on
- spaces</span> the value of the <code
- title="attr-head-profile">profile</code> attribute.</p></li>
-
- <li><p><span title="resolve a url">Resolve</span> each resulting
- token relative to the <code>head</code> element.</p></li>
-
- <li><p>For each token that is successfully resolved,
- <span>fetch</span> the resulting <span>absolute URL</span> and
- apply the appropriate processing.</p></li> <!-- http-origin privacy
- sensitive -->
-
- </ol>
-
<p>The <dfn title="dom-head-profile"><code>profile</code></dfn> IDL
attribute of the <code>head</code> element must <span>reflect</span>
the content attribute of the same name, as if the attribute's value
- was just a string. (In other words, the value is not <span
- title="resolve a url">resolved</span> in any way on getting.)</p>
+ was just a string.</p>
+
+ <p class="note">In other words, the value is not <span
+ title="resolve a url">resolved</span> in any way on getting. This is
+ mentioned explicitly merely because in earlier versions of HTML, the
+ attribute was defined as taking a <span>URL</span>.</p>
<hr>

0 comments on commit 4961080

Please sign in to comment.