Skip to content

Commit

Permalink
add IDs to be able to link to them from the wiki
Browse files Browse the repository at this point in the history 
git-svn-id: http://svn.whatwg.org/webapps@426 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Dec 8, 2006
1 parent 82fb0d0 commit 1cccf4d
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 23 deletions.
42 changes: 21 additions & 21 deletions index
View file
Expand Up @@ -394,8 +394,8 @@
<li><a href="#the-link"><span class=secno>3.8.4. </span>The <dfn
id=link><code>link</code></dfn> element</a>

<li><a href="#the-meta"><span class=secno>3.8.5. </span>The <dfn
id=meta><code>meta</code></dfn> element</a>
<li><a href="#meta"><span class=secno>3.8.5. </span>The <dfn
id=meta0><code>meta</code></dfn> element</a>
<ul class=toc>
<li><a href="#standard"><span class=secno>3.8.5.1. </span>Standard
metadata names</a>
Expand Down Expand Up @@ -2690,7 +2690,7 @@ should the click, focus, blur methods be recursible?
XXX--><code><a
href="#iframe0">iframe</a></code>, <code><a href="#img0">img</a></code>,
<code>input</code>, <code><a href="#map0">map</a></code>, <code><a
href="#meta0">meta</a></code>, <code><a
href="#meta1">meta</a></code>, <code><a
href="#object0">object</a></code>,<!-- param?
XXX-->
<code>select</code>, and <code>textarea</code> elements in that document
Expand Down Expand Up @@ -3037,7 +3037,7 @@ should the click, focus, blur methods be recursible?
href="#col0">col</a></code>, <code><a href="#embed0">embed</a></code>,
<code>frame</code>, <code><a href="#hr0">hr</a></code>, <code><a
href="#img0">img</a></code>, <code>input</code>, <code><a
href="#link0">link</a></code>, <code><a href="#meta0">meta</a></code>,
href="#link0">link</a></code>, <code><a href="#meta1">meta</a></code>,
<code><a href="#param0">param</a></code>, <code>spacer</code>, or
<code>wbr</code>, then continue on to the next child node at this
point.</p>
Expand Down Expand Up @@ -6512,7 +6512,7 @@ class="main"> or <div class="content">. Why do we also need a body?
element, optionally one <code><a href="#base0">base</a></code> element
(HTML only), and zero or more other <a href="#metadata2">metadata
elements</a> (in particular, <code><a href="#link0">link</a></code>,
<code><a href="#meta0">meta</a></code>, <code><a
<code><a href="#meta1">meta</a></code>, <code><a
href="#style0">style</a></code>, and <code><a
href="#script2">script</a></code>).

Expand Down Expand Up @@ -6915,8 +6915,8 @@ class="main"> or <div class="content">. Why do we also need a body?
return false and must do nothing on setting.</p>
<!-- XXX xref -->

<h4 id=the-meta><span class=secno>3.8.5. </span>The <dfn
id=meta0><code>meta</code></dfn> element</h4>
<h4 id=meta><span class=secno>3.8.5. </span>The <dfn
id=meta1><code>meta</code></dfn> element</h4>

<p><a href="#metadata2" title="metadata elements">Metadata element</a>.

Expand Down Expand Up @@ -6952,28 +6952,28 @@ class="main"> or <div class="content">. Why do we also need a body?
};</pre>
</dl>

<p>The <code><a href="#meta0">meta</a></code> element allows authors to
<p>The <code><a href="#meta1">meta</a></code> element allows authors to
specify document metadata that cannot be expressed using the <code><a
href="#title2">title</a></code>, <code><a href="#base0">base</a></code>,
<code><a href="#link0">link</a></code>, <code><a
href="#style0">style</a></code>, and <code><a
href="#script2">script</a></code> elements. The metadata is expressed in
terms of name/value pairs: the <dfn id=name
title=attr-meta-name><code>name</code></dfn> attribute on the <code><a
href="#meta0">meta</a></code> element gives the name, and the <dfn
href="#meta1">meta</a></code> element gives the name, and the <dfn
id=content0 title=attr-meta-content><code>content</code></dfn> attribute
on the same element gives the value.

<p>If a <code><a href="#meta0">meta</a></code> element has no <code
<p>If a <code><a href="#meta1">meta</a></code> element has no <code
title=attr-meta-name><a href="#name">name</a></code> attribute, it does
not set document metadata. If a <code><a href="#meta0">meta</a></code>
not set document metadata. If a <code><a href="#meta1">meta</a></code>
element has no <code title=attr-meta-content><a
href="#content0">content</a></code> attribute, then the value part of the
metadata name/value pair is the empty string.

<p>The value must not be a URI. Links must be represented using the
<code><a href="#link0">link</a></code> element, not the <code><a
href="#meta0">meta</a></code> element.
href="#meta1">meta</a></code> element.

<p>The DOM attributes <dfn id=name0
title=dom-meta-name><code>name</code></dfn> and <dfn id=content1
Expand All @@ -6985,7 +6985,7 @@ class="main"> or <div class="content">. Why do we also need a body?

<p>This specification defines a few names for the <code
title=attr-meta-name><a href="#name">name</a></code> attribute of the
<code><a href="#meta0">meta</a></code> element.
<code><a href="#meta1">meta</a></code> element.

<dl>
<dt><dfn id=generator title=meta-generator>generator</dfn>
Expand Down Expand Up @@ -7076,10 +7076,10 @@ class="main"> or <div class="content">. Why do we also need a body?
<h5 id=charset><span class=secno>3.8.5.3. </span>Specifying and
establishing the document's character encoding</h5>

<p>The <code><a href="#meta0">meta</a></code> element may also be used, in
<p>The <code><a href="#meta1">meta</a></code> element may also be used, in
HTML only (not in XHTML) to provide UAs with character encoding
information for the file. To do this, the <code><a
href="#meta0">meta</a></code> element must be the first element in the
href="#meta1">meta</a></code> element must be the first element in the
<code><a href="#head0">head</a></code> element, it must have the <dfn
id=http-equiv title=attr-meta-http-equiv><code>http-equiv</code></dfn>
attribute set to the literal value <code title="">Content-Type</code>, and
Expand All @@ -7089,7 +7089,7 @@ class="main"> or <div class="content">. Why do we also need a body?
encoding, which must be a valid character encoding name. <a
href="#refsIANACHARSET">[IANACHARSET]</a> <!-- XXX
http://www.iana.org/assignments/character-sets -->
When the <code><a href="#meta0">meta</a></code> element is used in this
When the <code><a href="#meta1">meta</a></code> element is used in this
way, there must be no other attributes set on the element, and the
<code>http-equiv</code> attribute must be listed first in the source.
Other than for giving the document's character encoding in this way, the
Expand Down Expand Up @@ -25603,7 +25603,7 @@ function receiver(e) {
<dt>Void elements

<dd><code><a href="#base0">base</a></code>, <code><a
href="#link0">link</a></code>, <code><a href="#meta0">meta</a></code>,
href="#link0">link</a></code>, <code><a href="#meta1">meta</a></code>,
<code><a href="#hr0">hr</a></code>, <code><a href="#br0">br</a></code>,
<code><a href="#img0">img</a></code>, <code><a
href="#embed0">embed</a></code>, <code><a
Expand Down Expand Up @@ -26244,7 +26244,7 @@ function receiver(e) {
<li>If the transport layer specifies an encoding, use that.

<li>Otherwise, if the user agent can find a <code><a
href="#meta0">meta</a></code> element that <a href="#charset">specifies
href="#meta1">meta</a></code> element that <a href="#charset">specifies
character encoding information</a>, then use that. (The exact parsing
rules for finding and using this information are not yet described in
this specification.) <span class=big-issue>This needs to be fleshed out a
Expand Down Expand Up @@ -27249,7 +27249,7 @@ function receiver(e) {
that is immediately followed by a U+003E GREATER-THAN SIGN, if, and only
if, the current token being processed is a start tag token whose tag name
is one of the following: <code><a href="#base0">base</a></code>, <code><a
href="#link0">link</a></code>, <code><a href="#meta0">meta</a></code>,
href="#link0">link</a></code>, <code><a href="#meta1">meta</a></code>,
<code><a href="#hr0">hr</a></code>, <code><a href="#br0">br</a></code>,
<code><a href="#img0">img</a></code>, <code><a
href="#embed0">embed</a></code>, <code><a href="#param0">param</a></code>,
Expand Down Expand Up @@ -27615,7 +27615,7 @@ http://trac.webkit.org/projects/webkit/browser/trunk/WebCore/html/HTMLTokenizer.
<code><a href="#img0">img</a></code>, <code>input</code>,
<code>isindex</code>, <code><a href="#li0">li</a></code>, <code><a
href="#link0">link</a></code>, <code>listing</code>, <code><a
href="#menu0">menu</a></code>, <code><a href="#meta0">meta</a></code>,
href="#menu0">menu</a></code>, <code><a href="#meta1">meta</a></code>,
<code>noembed</code>, <code>noframes</code>, <code><a
href="#noscript0">noscript</a></code>, <code><a
href="#ol0">ol</a></code>, <code>optgroup</code>, <code>option</code>,
Expand Down Expand Up @@ -28192,7 +28192,7 @@ simplified explanation instead:
href="#current3">current node</a> being a <code><a
href="#head0">head</a></code> element, e.g. if a <code><a
href="#head0">head</a></code> end tag is immediately followed by a
<code><a href="#meta0">meta</a></code> start tag.</p>
<code><a href="#meta1">meta</a></code> start tag.</p>

<dl class=switch>
<dt>A character token that is one of one of U+0009 CHARACTER
Expand Down
4 changes: 2 additions & 2 deletions source
View file
Expand Up @@ -4757,7 +4757,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E..
</dl>


<h3>Classes</h3>
<h3 id="classes">Classes</h3>

<p>Every <span>HTML element</span> may have a <dfn
title="attr-class"><code>class</code></dfn> attribute specified.</p>
Expand Down Expand Up @@ -5750,7 +5750,7 @@ class="main"> or <div class="content">. Why do we also need a body?
return false and must do nothing on setting.</p> <!-- XXX xref -->


<h4>The <dfn><code>meta</code></dfn> element</h4>
<h4 id="meta">The <dfn><code>meta</code></dfn> element</h4>

<p><span title="metadata elements">Metadata element</span>.</p>

Expand Down

0 comments on commit 1cccf4d

Please sign in to comment.