test/html-webhacc/standards.en.html

<!DOCTYPE HTML>
<html lang=en>
<head>
<title>WebHACC &mdash; Supported Standards</title>
<link rel=stylesheet href=cc-style>
</head>
<body>

<h1><a href="cc/"><abbr title="Web Hypertext Application Conformance
Checker"><img src="icons/title" alt="WebHACC"></abbr></a></h1>

<div class=section id=standards>
<h2>Supported Standards</h2>

<p>The table below summarizes Web standards supported by WebHACC.  See
following subsections for more details.

<table>
<thead>
<tr><th scope=col>Standard<th scope=col>Version<th scope=col>Note
</thead>
<tbody>
<tr><th scope=row><a href="#html"><abbr title="Hypertext Markup Language">HTML</abbr></a>
<td rowspan=2><a href="http://whatwg.org/html5">HTML5 Draft Recommendation</a>
<td rowspan=2>Most parts

<tr><th><a href="#html">XHTML</a>

<tr><th rowspan=2><a href="#atom">Atom</a>
<td><a href="urn:ietf:rfc:4287">Atom 1.0 <abbr>RFC</abbr></a>
<td><!-- Full -->

<tr><td><a href="urn:ietf:rfc:4685">Atom Threading 1.0 <abbr>RFC</abbr></a>

<tr><th scope=row rowspan=2><abbr title="Extensible Markup Language">XML</abbr>
<td>1.0 Fourth Edition
<td>Tentative
<tr><td>1.1 Second Edition
<td>Tentative
<tr><th scope=row rowspan=2><abbr title="Extensible Markup Language">XML</abbr>
Namespaces
<td>1.0 Second Edition
<td>Tentative
<tr><td>1.1 First Edition
<td>Tentative

<tr>
<th rowspan=2><a href="#css"><abbr title="Cascading Style Sheets">CSS</abbr></a>
<td><a href="http://www.w3.org/TR/2007/CR-CSS21-20070719/">CSS 2.1
Candidate Recommendation</a>
<td>Most parts

<tr>
<td><a href="http://www.w3.org/TR/2008/WD-css3-color-20080721/">CSS Color
Level 3 <abbr title="Last Call Working Draft">LCWD</abbr></a>
<td>Most parts

<tr>
<th scope=row>Selectors
<td>3
<td><!-- Full -->
</tbody>

<tbody>
<tr><th><a href="#cache-manifest">Cache Manifest</a>
<td><a href="http://www.whatwg.org/specs/web-apps/current-work/#manifests">HTML5
Draft Recommendation</a>
<td><!-- Full -->

<tr><th><a href="#webidl">WebIDL</a>
<td><a href="http://dev.w3.org/cvsweb/~checkout~/2006/webapi/WebIDL/Overview.html?rev=1.96&amp;content-type=text/html;%20charset=utf-8">Editor's
Draft 1.96</a>
<td><!-- Full -->

<tbody>
<tr><th scope=row><abbr title="Hypertext Transfer Protocol">HTTP</abbr>
<td>
<td>Tentative (no validation)
</tbody>
</table>

<div class=section id=dom>
<h3><abbr title="Document Object Model">DOM</abbr></h3>

<p>The current implementation assumes that there are following 
requirements:</p>
<ul>
<li>The document element (or root element) <em class=rfc2119>MUST</em>
be allowed to be a root element.  <span class=example>For example,
an <code>html</code> element in <code>http://www.w3.org/1999/xhtml</code>
namespace is allowed to be a root element by the HTML5
specification.</span></li>
</ul>
</div>

<div class=section id=html>
<h3><abbr title="Hypertext Markup Language">HTML</abbr></h3>

<p>HTML5 is partially implemented.</p>

<p>In addition, the current implementation assumes that there are following 
requirements:</p>
<ul>
<li>Any attribute in the HTML namespace which is not defined by the
HTML5 specification (including Web Forms 2.0 specification) 
<em class=rfc2119>MUST NOT</em> be used.</li>
<li>For an element in the HTML namespace, any attribute in the null namespace
(or per$B!>(Belement partition) <em class=rfc2119>MUST NOT</em> be used
unless it is allowed by the HTML5 specification (including Web Forms 2.0
specification).</li>
<li class=ed>@@ Forms elements: ...

<li>For the attribute not defined in HTML5, the following definitions are
applied.

  <div class="note memo">
  <p>These definitions are updated version of their original definitions
  in previous versions of HTML (i.e. HTML 2.x, HTML4, Web Forms 2.0,
  or early drafts of HTML5).
  </div>

  <p>For each row in the table below, if an attribute (i.e. an
  <code>Attr</code> node) met the following conditions, then the
  <code>value</code> attribute value of the node <em class=rfc2119>MUST</em>
  be valid with regard to the constraints shown in the <q>Value</q>
  cell of the row.  The conditions are:
    <ul>
    <li>There is an owner element (i.e. the <code>Element</code> node
    pointed by the <code>ownerElement</code> attribute of the 
    <code>Attr</code> node).
    <li>The <code>namespaceURI</code> attribute value of the owner element
    is <code>http://www.w3.org/1999/xhtml</code>.
    <li>The <code>manakaiLocalName</code> attribute value [@@ TODO: ref]
    of the owner element is equal to the value in the <q>Element</q> cell
    of the row.
    <li>The <code>namespaceURI</code> attribute value of the <code>Attr</code>
    node is <code>null</code>.
    <li>The <code>manakaiLocalName</code> attribute value of the
    <code>Attr</code> node is equal to the value in the <q>Attribute</q>
    cell of the row.
    </ul>

  <table>
  <thead>
  <tr><th scope=row>Element<th scope=row>Attribute
  <th scope=row>Value
  <tbody>
  <tr><td><code>body</code><td><code>background</code>
  <td>Syntactically same as <code>img</code> <code>src</code> [HTML5]
  <tr><td><code>img</code><td><code>longdesc</code>
  <td>Syntactically same as <code>img</code> <code>src</code> [HTML5]

  <tr><td><code>input</code><td><code>accept-charset</code>
  <td>Same as <code>accept-charset</code> attribute of the
  <code>form</code> element [HTML5]

  <tr><td><code>input</code> (<code>type</code> attribute is in Image Button
  state)
  <td><code>usemap</code>
  <td>Syntactically same as <code>img</code> <code>usemap</code> [HTML5]
  <!-- This definition is necessary, since HTML5 definition for usemap=""
  has changed after <input usemap> is dropped. -->

  <tr><td><code>object</code><td><code>classid</code> or <code>codebase</code>
  <td>Syntactically same as <code>img</code> <code>src</code> [HTML5]

  <tr><td><code>head</code><td><code>profile</code>
  <td>Same as <code>a</code> <code>ping</code> [HTML5]
  <!-- This definition is necessary, since HTML5 defnition for attributes
  with URLs has changed after profile="" is dropped. -->

  <tr><td><code>object</code><td><code>archive</code>
  <td>Same as <code>a</code> <code>ping</code> [HTML5]

  <tr><td><code>object</code><td><code>codetype</code>
  <td>Same as <code>object</code> <code>type</code> [HTML5]
  <tr><td><code>param</code><td><code>type</code>
  <td>Same as <code>object</code> <code>type</code> [HTML5]
  <tr><td><code>address</code>, <code>div</code>, <code>h1</code>,
  <code>h2</code>, <code>h3</code>, <code>h4</code>, <code>h5</code>,
  <code>h6</code>, or <code>p</code>
  <td><code>align</code>
  <td>Enumerated attribute [HTML5]

  <tr><td><code>img</code> or <code>object</code><td><code>align</code>
  <td>Enumerated attribute [HTML5]

  <tr><td><code>input</code> (<code>type</code> attribute is in
  Image Button state)
  <td><code>align</code>
  <td>Enumerated attribute [HTML5], where keywords are: <code>top</code>,
  <code>middle</code>, <code>bottom</code>, <code>left</code>,
  <code>right</code><!-- Same as HTML4 Transitional DTD definition.  See
  also comment below. -->

  <tr><td><code>br</code><td><code>clear</code>
  <td>Enumerated attribute [HTML5]
  <tr><td><code>param</code><td><code>valuetype</code>
  <td>Enumerated attribute [HTML5]
  <tr><td><code>pre</code><td><code>width</code>
  <td>Valid non-negative integer [HTML5]
  <tr><td><code>ul</code>, <code>ol</code>, <code>dir</code>,
  <code>menu</code>, or <code>dl</code><td><code>compact</code>
  <td>Boolean attribute [HTML5]

  <tr><td><code>input</code> (<code>type</code> attribute is in Image
  Button<!-- @@ ref --> state)
  <td><code>ismap</code>
  <td>Boolean attribute [HTML5]

  <tr><td><code>table</code><td><code>frame</code> or <code>rules</code>
  <td>Enumerated attribute [HTML5]
  <tr><td><code>td</code><td><code>scope</code>
  <td>Same as <code>scope</code> attribute of the <code>th</code> element
  [HTML5]
  <tr><td><code>tbody</code>, <code>thead</code>, <code>tfoot</code>,
  <code>colgroup</code>, <code>col</code>, <code>tr</code>, <code>td</code>,
  or <code>th</code><td><code>align</code> or <code>valign</code>
  <td>Enumerated attribute [HTML5]

  <tr><td><code>input</code> (<code>type</code> attribute is in
  Image Button<!-- @@ ref --> or Submit Button<!-- @@ ref --> state)
  <td><code>replace</code>
  <td>Enumerated attribute [HTML5]

  <tr><td><code>link</code><td><code>target</code>
  <td>Valid browsing context name or keyword [HTML5]
  <tr id=html-meta-scheme><td><code>meta</code><td><code>schema</code>
  <td>Any string
  <!--
    NOTE: According to HTML4, values for the |scheme| attribute
    depend on |name| attribute and |profile| of |head|.  Otherwise
    it is "cdata".  The only profile with any scheme value defined
    is <http://dublincore.org/documents/dcq-html/> (and those
    references that profile; see
    <http://suika.fam.cx/gate/2005/sw/scheme#anchor-55> for more
    information).
  -->
  <tr id=html-rev><td><code>a</code> or <code>link</code><td><code>rev</code>
  <td>Unordered set of unique space-separated tokens [HTML5]
  (where any word is allowed)
  <tr id=html-table-cellpadding><td rowspan=2><code>table</code>
  <td><code>cellpadding</code>
  <td rowspan=2>A non-negative integer [HTML5] or a non-negative integer
  [HTML5] followed by a <code>%</code> character
  <tr id=html-table-cellspacing><td><code>cellspacing</code>
  <tr id=html-a-charset><td><code>a</code>
  <td rowspan=2><code>charset</code>
  <td rowspan=2>Same as <code>script</code> <code>charset</code> [HTML5],
  syntactically
  <tr id=html-link-charset><td><code>link</code>
  </table>
<li>Any value <em class=rfc2119>MAY</em> be specified to the
<code>version</code> attribute of an <code>html</code> element.
<li>@@ elements ...

  <table>
  <thead>
  <tr><th scope=row>Element<th scope=row>Content Model
  <th scope=row>Allowed Context
  <tbody>
  <tr><th scope=col><code>center</code>
  <td colspan=2>Same as <code>div</code> [HTML5]
  </table>
</ul>

<p>For an <code>input</code> element whose <code>type</code> attribute
is <code>add</code>, <code>remove</code>, <code>move-up</code>, or
<code>move-down</code> (ASCII case-insensitive<!-- ref -->) [WF2],
attributes that is not allowed for an <code>input</code> element whose
<code>type</code> attribute is in the Button state<!-- ref --> <em
class=rfc2119>MUST NOT</em> be specified.<!-- Whether an attribute is
applicable or not is normatively defined in the table in the Appendix
B of the Web Forms 2.0 specification.  However, there is no clause
that states that use of an attribute that is not applied is
non-conforming.  Note that the <code>template</code> attribute, which
is applied to the <code>add</code> attribute according to Web Forms
2.0, is defined as a global attribute (with different semantics and
syntax) by HTML5 as part of the data template feature. -->

<p>The <code>inputmode</code> attribute applies to an
<code>input</code> element in Text, E-mail, URL, or Password<!-- @@
refs --> state.  The <code>replace</code> attribute applies to an
<code>input</code> element in Image Button or Submit Button<!-- @@
refs --> state.<!-- In WF2 normative table, but no MUST NOT there. -->
The <code>usemap</code> attribute applies to an <code>input</code>
element in Image Button<!-- @@ ref --> state.<!-- In HTML5 prior to
r997, usemap="" MAY be specified to an input element with Image (now
Image Button) state, but Image state was not defined yet and there
were no "MUST NOT".-->  The <code>align</code> attribute applies to an
<code>input</code> element in Image Button state.<!-- In HTML4, to
which state(s) this attribute is applied is not defined at all.  In
addition, the reference to the definition of the attribute is linked
to a wrong place (align attribute of p element and so on).  In HTML
2.x, DTD comment implies that this attribute applies to type=image.
In HTML 2.0, this attribute is only explained for type=image in the
prose.  --> Any of these attributes <em class=rfc2119>MUST NOT</em> be
specified for an <code>input</code> element whose <code>type</code>
attribute is in a state where the attribute does not apply.

<p id=cache-manifest>The 
<a href="http://www.whatwg.org/specs/web-apps/current-work/#manifests">cache
manifest syntax</a> is also supported.
</div>

<div class=section id=atom>
<h3>Atom</h3>

<p><a href="urn:ietf:rfc:4287">Atom 1.0</a> and 
<a href="urn:ietf:rfc:4685">Atom Threading 1.0</a> are supported.

<p>However, conformance to some <em class=rfc2119>SHOULD</em>-level
requirements, as well as some informational guidelines, are currently
not checked.  In addition, whether an email-address or a Base64
encoding is correct or not is not checked either.

<p>Use of XML digital signature and encryption is not supported.

<p>The current implementation assumes that there are following 
requirements:</p>
<ul>
<li>Elements and attributes in the Atom namespace, as well as attributes
in the null namespace for an element in the Atom namespace,
<em class=rfc2119>MUST NOT</em>
be used except for contexts where they are allowed by the Atom 
specification.</li>
<li>Inter-element whitespace [HTML5], processing instructions, and
comments <em class=rfc2119>MUST</em> be ignored for the purpose of 
conformance of the content of an element.
</ul>
</div>

<div class=section id=css>
<h3><abbr title="Cascading Style Sheets">CSS</abbr></h3>

<p>CSS @namespace and Selectors Level 3 are fully implemented.</p>

<p>Most of <a href="http://www.w3.org/TR/2007/CR-CSS21-20070719/">CSS 2.1
(<time datetime=2007-07-19>19 July 2007</time> Candidate Recommendation)</a>
is implemented.
<!-- @@ TODO: What is missing? -->

<p>Most of <a href="http://www.w3.org/TR/2008/WD-css3-color-20080721/">CSS 
Color Module Level 3 (<time datetime=2008-07-21>21 July 2008</time> Last
Call Working Draft)</a> is implemented.
<!-- @@ TODO: What is missing? -->

<p>Since the <abbr title="Cascading Style Sheets">CSS</abbr> 2.1
specification is sometimes ambigious or disagree with browsers,
our implementation is tend to copy what browsers do unless
there is strong resaon to do different thing.</p>

<p>In addition, the current implementation assumes that there are following 
requirements:</p>
<ul>
<li id=css-type-charset-param>The <code>charset</code> parameter of the media 
type <code>text/css</code> <em class=rfc2119>MUST</em> be treated as if it 
were an unknown parameter for the purpose of determining styling langauge for 
an <abbr>HTML</abbr> <code>style</code> element.</li>
<li id=css-style-content>Content of an <abbr>HTML</abbr> <code>style</code> 
element whose content is interpreted as a CSS style sheet 
<em class=rfc2119>MUST</em> consist of zero or more 
<a href="http://www.whatwg.org/specs/web-apps/current-work/#text-node">text nodes</a>.
Note that it may also contain zero or more comment and/or processing 
instruction nodes.</li>
</ul>

</div>

<div class=section id=regexp>
<h3>Regular expressions</h3>

<p>Regular expression defined in ECMAScript Third Edition Section
15.10.1 is implemented, with the addition of the support for obsolete
octal escape notation commonly supported by Web browsers.

<p>To identify ECMAScript regular expressions, the Internet Media Type
<a
href="http://suika.fam.cx/%7Ewakaba/wiki/sw/n/text+x-regexp-js"><code>text/x-regexp-js</code></a>
is used.

</div>

<div class=section id=webidl>
<h3>WebIDL</h3>

<p><a href="http://dev.w3.org/cvsweb/~checkout~/2006/webapi/WebIDL/Overview.html?rev=1.96&amp;content-type=text/html;%20charset=utf-8">WebIDL
Editor's Draft revision 1.96 (<time datetime=2008-09-03>3 September 
2008</time>)</a> is implemented.</p>
</div>

</div>

</body>
</html>
1	wakaba	1.1	<!DOCTYPE HTML>
2			<html lang=en>
3			<head>
4	wakaba	1.14	<title>WebHACC — Supported Standards</title>
5	wakaba	1.1	<link rel=stylesheet href=cc-style>
6			</head>
7			<body>
8
9	wakaba	1.14	<h1><a href="cc/"><abbr title="Web Hypertext Application Conformance
10			Checker"><img src="icons/title" alt="WebHACC"></abbr></a></h1>
11
12			<div class=section id=standards>
13			<h2>Supported Standards</h2>
14
15			<p>The table below summarizes Web standards supported by WebHACC. See
16			following subsections for more details.
17	wakaba	1.1
18			<table>
19			<thead>
20			<tr><th scope=col>Standard<th scope=col>Version<th scope=col>Note
21			</thead>
22			<tbody>
23			<tr><th scope=row><a href="#html"><abbr title="Hypertext Markup Language">HTML</abbr></a>
24	wakaba	1.11	<td rowspan=2><a href="http://whatwg.org/html5">HTML5 Draft Recommendation</a>
25			<td rowspan=2>Most parts
26
27			<tr><th><a href="#html">XHTML</a>
28
29			<tr><th rowspan=2><a href="#atom">Atom</a>
30			<td><a href="urn:ietf:rfc:4287">Atom 1.0 <abbr>RFC</abbr></a>
31			<td><!-- Full -->
32
33			<tr><td><a href="urn:ietf:rfc:4685">Atom Threading 1.0 <abbr>RFC</abbr></a>
34
35	wakaba	1.1	<tr><th scope=row rowspan=2><abbr title="Extensible Markup Language">XML</abbr>
36			<td>1.0 Fourth Edition
37			<td>Tentative
38			<tr><td>1.1 Second Edition
39			<td>Tentative
40			<tr><th scope=row rowspan=2><abbr title="Extensible Markup Language">XML</abbr>
41			Namespaces
42			<td>1.0 Second Edition
43			<td>Tentative
44			<tr><td>1.1 First Edition
45			<td>Tentative
46	wakaba	1.11
47	wakaba	1.2	<tr>
48	wakaba	1.11	<th rowspan=2><a href="#css"><abbr title="Cascading Style Sheets">CSS</abbr></a>
49			<td><a href="http://www.w3.org/TR/2007/CR-CSS21-20070719/">CSS 2.1
50			Candidate Recommendation</a>
51			<td>Most parts
52
53			<tr>
54			<td><a href="http://www.w3.org/TR/2008/WD-css3-color-20080721/">CSS Color
55			Level 3 <abbr title="Last Call Working Draft">LCWD</abbr></a>
56			<td>Most parts
57
58	wakaba	1.2	<tr>
59			<th scope=row>Selectors
60			<td>3
61			<td><!-- Full -->
62	wakaba	1.1	</tbody>
63	wakaba	1.11
64			<tbody>
65			<tr><th><a href="#cache-manifest">Cache Manifest</a>
66			<td><a href="http://www.whatwg.org/specs/web-apps/current-work/#manifests">HTML5
67			Draft Recommendation</a>
68			<td><!-- Full -->
69
70			<tr><th><a href="#webidl">WebIDL</a>
71			<td><a href="http://dev.w3.org/cvsweb/~checkout~/2006/webapi/WebIDL/Overview.html?rev=1.96&content-type=text/html;%20charset=utf-8">Editor's
72			Draft 1.96</a>
73			<td><!-- Full -->
74
75	wakaba	1.1	<tbody>
76			<tr><th scope=row><abbr title="Hypertext Transfer Protocol">HTTP</abbr>
77			<td>
78			<td>Tentative (no validation)
79			</tbody>
80			</table>
81
82	wakaba	1.3	<div class=section id=dom>
83	wakaba	1.14	<h3><abbr title="Document Object Model">DOM</abbr></h3>
84	wakaba	1.3
85			<p>The current implementation assumes that there are following
86			requirements:</p>
87			<ul>
88			<li>The document element (or root element) <em class=rfc2119>MUST</em>
89			be allowed to be a root element. <span class=example>For example,
90			an <code>html</code> element in <code>http://www.w3.org/1999/xhtml</code>
91			namespace is allowed to be a root element by the HTML5
92			specification.</span></li>
93			</ul>
94			</div>
95
96	wakaba	1.1	<div class=section id=html>
97	wakaba	1.14	<h3><abbr title="Hypertext Markup Language">HTML</abbr></h3>
98	wakaba	1.1
99	wakaba	1.3	<p>HTML5 is partially implemented.</p>
100
101	wakaba	1.4	<p>In addition, the current implementation assumes that there are following
102			requirements:</p>
103	wakaba	1.1	<ul>
104	wakaba	1.9	<li>Any attribute in the HTML namespace which is not defined by the
105	wakaba	1.7	HTML5 specification (including Web Forms 2.0 specification)
106			<em class=rfc2119>MUST NOT</em> be used.</li>
107	wakaba	1.4	<li>For an element in the HTML namespace, any attribute in the null namespace
108			(or per$B!>(Belement partition) <em class=rfc2119>MUST NOT</em> be used
109			unless it is allowed by the HTML5 specification (including Web Forms 2.0
110			specification).</li>
111			<li class=ed>@@ Forms elements: ...
112	wakaba	1.5
113			<li>For the attribute not defined in HTML5, the following definitions are
114			applied.
115
116			<div class="note memo">
117			<p>These definitions are updated version of their original definitions
118	wakaba	1.13	in previous versions of HTML (i.e. HTML 2.x, HTML4, Web Forms 2.0,
119			or early drafts of HTML5).
120	wakaba	1.5	</div>
121
122			<p>For each row in the table below, if an attribute (i.e. an
123			<code>Attr</code> node) met the following conditions, then the
124			<code>value</code> attribute value of the node <em class=rfc2119>MUST</em>
125			be valid with regard to the constraints shown in the <q>Value</q>
126			cell of the row. The conditions are:
127			<ul>
128			<li>There is an owner element (i.e. the <code>Element</code> node
129			pointed by the <code>ownerElement</code> attribute of the
130			<code>Attr</code> node).
131			<li>The <code>namespaceURI</code> attribute value of the owner element
132			is <code>http://www.w3.org/1999/xhtml</code>.
133			<li>The <code>manakaiLocalName</code> attribute value [@@ TODO: ref]
134			of the owner element is equal to the value in the <q>Element</q> cell
135			of the row.
136			<li>The <code>namespaceURI</code> attribute value of the <code>Attr</code>
137			node is <code>null</code>.
138			<li>The <code>manakaiLocalName</code> attribute value of the
139			<code>Attr</code> node is equal to the value in the <q>Attribute</q>
140			cell of the row.
141			</ul>
142
143			<table>
144			<thead>
145			<tr><th scope=row>Element<th scope=row>Attribute
146			<th scope=row>Value
147			<tbody>
148			<tr><td><code>body</code><td><code>background</code>
149	wakaba	1.13	<td>Syntactically same as <code>img</code> <code>src</code> [HTML5]
150	wakaba	1.5	<tr><td><code>img</code><td><code>longdesc</code>
151	wakaba	1.13	<td>Syntactically same as <code>img</code> <code>src</code> [HTML5]
152	wakaba	1.12
153			<tr><td><code>input</code><td><code>accept-charset</code>
154			<td>Same as <code>accept-charset</code> attribute of the
155			<code>form</code> element [HTML5]
156
157	wakaba	1.13	<tr><td><code>input</code> (<code>type</code> attribute is in Image Button
158			state)
159			<td><code>usemap</code>
160			<td>Syntactically same as <code>img</code> <code>usemap</code> [HTML5]
161			<!-- This definition is necessary, since HTML5 definition for usemap=""
162			has changed after <input usemap> is dropped. -->
163
164	wakaba	1.5	<tr><td><code>object</code><td><code>classid</code> or <code>codebase</code>
165	wakaba	1.13	<td>Syntactically same as <code>img</code> <code>src</code> [HTML5]
166
167			<tr><td><code>head</code><td><code>profile</code>
168	wakaba	1.5	<td>Same as <code>a</code> <code>ping</code> [HTML5]
169	wakaba	1.13	<!-- This definition is necessary, since HTML5 defnition for attributes
170			with URLs has changed after profile="" is dropped. -->
171
172			<tr><td><code>object</code><td><code>archive</code>
173			<td>Same as <code>a</code> <code>ping</code> [HTML5]
174
175	wakaba	1.5	<tr><td><code>object</code><td><code>codetype</code>
176			<td>Same as <code>object</code> <code>type</code> [HTML5]
177			<tr><td><code>param</code><td><code>type</code>
178			<td>Same as <code>object</code> <code>type</code> [HTML5]
179	wakaba	1.10	<tr><td><code>address</code>, <code>div</code>, <code>h1</code>,
180			<code>h2</code>, <code>h3</code>, <code>h4</code>, <code>h5</code>,
181			<code>h6</code>, or <code>p</code>
182	wakaba	1.5	<td><code>align</code>
183			<td>Enumerated attribute [HTML5]
184	wakaba	1.13
185	wakaba	1.5	<tr><td><code>img</code> or <code>object</code><td><code>align</code>
186			<td>Enumerated attribute [HTML5]
187	wakaba	1.13
188			<tr><td><code>input</code> (<code>type</code> attribute is in
189			Image Button state)
190			<td><code>align</code>
191			<td>Enumerated attribute [HTML5], where keywords are: <code>top</code>,
192			<code>middle</code>, <code>bottom</code>, <code>left</code>,
193			<code>right</code><!-- Same as HTML4 Transitional DTD definition. See
194			also comment below. -->
195
196	wakaba	1.5	<tr><td><code>br</code><td><code>clear</code>
197			<td>Enumerated attribute [HTML5]
198			<tr><td><code>param</code><td><code>valuetype</code>
199			<td>Enumerated attribute [HTML5]
200			<tr><td><code>pre</code><td><code>width</code>
201			<td>Valid non-negative integer [HTML5]
202			<tr><td><code>ul</code>, <code>ol</code>, <code>dir</code>,
203			<code>menu</code>, or <code>dl</code><td><code>compact</code>
204			<td>Boolean attribute [HTML5]
205	wakaba	1.13
206			<tr><td><code>input</code> (<code>type</code> attribute is in Image
207			Button<!-- @@ ref --> state)
208			<td><code>ismap</code>
209			<td>Boolean attribute [HTML5]
210
211	wakaba	1.5	<tr><td><code>table</code><td><code>frame</code> or <code>rules</code>
212			<td>Enumerated attribute [HTML5]
213			<tr><td><code>td</code><td><code>scope</code>
214			<td>Same as <code>scope</code> attribute of the <code>th</code> element
215			[HTML5]
216			<tr><td><code>tbody</code>, <code>thead</code>, <code>tfoot</code>,
217			<code>colgroup</code>, <code>col</code>, <code>tr</code>, <code>td</code>,
218			or <code>th</code><td><code>align</code> or <code>valign</code>
219			<td>Enumerated attribute [HTML5]
220	wakaba	1.13
221			<tr><td><code>input</code> (<code>type</code> attribute is in
222			Image Button<!-- @@ ref --> or Submit Button<!-- @@ ref --> state)
223			<td><code>replace</code>
224			<td>Enumerated attribute [HTML5]
225
226	wakaba	1.5	<tr><td><code>link</code><td><code>target</code>
227	wakaba	1.6	<td>Valid browsing context name or keyword [HTML5]
228	wakaba	1.5	<tr id=html-meta-scheme><td><code>meta</code><td><code>schema</code>
229			<td>Any string
230			<!--
231			NOTE: According to HTML4, values for the \|scheme\| attribute
232			depend on \|name\| attribute and \|profile\| of \|head\|. Otherwise
233			it is "cdata". The only profile with any scheme value defined
234			is <http://dublincore.org/documents/dcq-html/> (and those
235			references that profile; see
236			<http://suika.fam.cx/gate/2005/sw/scheme#anchor-55> for more
237			information).
238			-->
239	wakaba	1.8	<tr id=html-rev><td><code>a</code> or <code>link</code><td><code>rev</code>
240	wakaba	1.5	<td>Unordered set of unique space-separated tokens [HTML5]
241			(where any word is allowed)
242	wakaba	1.8	<tr id=html-table-cellpadding><td rowspan=2><code>table</code>
243			<td><code>cellpadding</code>
244			<td rowspan=2>A non-negative integer [HTML5] or a non-negative integer
245			[HTML5] followed by a <code>%</code> character
246			<tr id=html-table-cellspacing><td><code>cellspacing</code>
247	wakaba	1.9	<tr id=html-a-charset><td><code>a</code>
248			<td rowspan=2><code>charset</code>
249			<td rowspan=2>Same as <code>script</code> <code>charset</code> [HTML5],
250			syntactically
251			<tr id=html-link-charset><td><code>link</code>
252	wakaba	1.5	</table>
253			<li>Any value <em class=rfc2119>MAY</em> be specified to the
254			<code>version</code> attribute of an <code>html</code> element.
255			<li>@@ elements ...
256
257			<table>
258			<thead>
259			<tr><th scope=row>Element<th scope=row>Content Model
260			<th scope=row>Allowed Context
261			<tbody>
262			<tr><th scope=col><code>center</code>
263			<td colspan=2>Same as <code>div</code> [HTML5]
264			</table>
265	wakaba	1.1	</ul>
266	wakaba	1.13
267			<p>For an <code>input</code> element whose <code>type</code> attribute
268			is <code>add</code>, <code>remove</code>, <code>move-up</code>, or
269			<code>move-down</code> (ASCII case-insensitive<!-- ref -->) [WF2],
270			attributes that is not allowed for an <code>input</code> element whose
271			<code>type</code> attribute is in the Button state<!-- ref --> <em
272			class=rfc2119>MUST NOT</em> be specified.<!-- Whether an attribute is
273			applicable or not is normatively defined in the table in the Appendix
274			B of the Web Forms 2.0 specification. However, there is no clause
275			that states that use of an attribute that is not applied is
276			non-conforming. Note that the <code>template</code> attribute, which
277			is applied to the <code>add</code> attribute according to Web Forms
278			2.0, is defined as a global attribute (with different semantics and
279			syntax) by HTML5 as part of the data template feature. -->
280
281			<p>The <code>inputmode</code> attribute applies to an
282			<code>input</code> element in Text, E-mail, URL, or Password<!-- @@
283			refs --> state. The <code>replace</code> attribute applies to an
284			<code>input</code> element in Image Button or Submit Button<!-- @@
285			refs --> state.<!-- In WF2 normative table, but no MUST NOT there. -->
286			The <code>usemap</code> attribute applies to an <code>input</code>
287			element in Image Button<!-- @@ ref --> state.<!-- In HTML5 prior to
288			r997, usemap="" MAY be specified to an input element with Image (now
289			Image Button) state, but Image state was not defined yet and there
290			were no "MUST NOT".--> The <code>align</code> attribute applies to an
291			<code>input</code> element in Image Button state.<!-- In HTML4, to
292			which state(s) this attribute is applied is not defined at all. In
293			addition, the reference to the definition of the attribute is linked
294			to a wrong place (align attribute of p element and so on). In HTML
295			2.x, DTD comment implies that this attribute applies to type=image.
296			In HTML 2.0, this attribute is only explained for type=image in the
297			prose. --> Any of these attributes <em class=rfc2119>MUST NOT</em> be
298			specified for an <code>input</code> element whose <code>type</code>
299			attribute is in a state where the attribute does not apply.
300	wakaba	1.11
301			<p id=cache-manifest>The
302			<a href="http://www.whatwg.org/specs/web-apps/current-work/#manifests">cache
303			manifest syntax</a> is also supported.
304	wakaba	1.1	</div>
305
306			<div class=section id=atom>
307	wakaba	1.14	<h3>Atom</h3>
308	wakaba	1.1
309	wakaba	1.11	<p><a href="urn:ietf:rfc:4287">Atom 1.0</a> and
310			<a href="urn:ietf:rfc:4685">Atom Threading 1.0</a> are supported.
311
312			<p>However, conformance to some <em class=rfc2119>SHOULD</em>-level
313			requirements, as well as some informational guidelines, are currently
314			not checked. In addition, whether an email-address or a Base64
315			encoding is correct or not is not checked either.
316
317			<p>Use of XML digital signature and encryption is not supported.
318
319	wakaba	1.5	<p>The current implementation assumes that there are following
320	wakaba	1.4	requirements:</p>
321			<ul>
322			<li>Elements and attributes in the Atom namespace, as well as attributes
323			in the null namespace for an element in the Atom namespace,
324			<em class=rfc2119>MUST NOT</em>
325			be used except for contexts where they are allowed by the Atom
326			specification.</li>
327			<li>Inter-element whitespace [HTML5], processing instructions, and
328			comments <em class=rfc2119>MUST</em> be ignored for the purpose of
329			conformance of the content of an element.
330			</ul>
331	wakaba	1.2	</div>
332
333			<div class=section id=css>
334	wakaba	1.14	<h3><abbr title="Cascading Style Sheets">CSS</abbr></h3>
335	wakaba	1.2
336	wakaba	1.3	<p>CSS @namespace and Selectors Level 3 are fully implemented.</p>
337
338	wakaba	1.11	<p>Most of <a href="http://www.w3.org/TR/2007/CR-CSS21-20070719/">CSS 2.1
339			(<time datetime=2007-07-19>19 July 2007</time> Candidate Recommendation)</a>
340			is implemented.
341			<!-- @@ TODO: What is missing? -->
342
343			<p>Most of <a href="http://www.w3.org/TR/2008/WD-css3-color-20080721/">CSS
344			Color Module Level 3 (<time datetime=2008-07-21>21 July 2008</time> Last
345			Call Working Draft)</a> is implemented.
346			<!-- @@ TODO: What is missing? -->
347	wakaba	1.3
348			<p>Since the <abbr title="Cascading Style Sheets">CSS</abbr> 2.1
349			specification is sometimes ambigious or disagree with browsers,
350			our implementation is tend to copy what browsers do unless
351			there is strong resaon to do different thing.</p>
352
353			<p>In addition, the current implementation assumes that there are following
354	wakaba	1.2	requirements:</p>
355			<ul>
356			<li id=css-type-charset-param>The <code>charset</code> parameter of the media
357			type <code>text/css</code> <em class=rfc2119>MUST</em> be treated as if it
358			were an unknown parameter for the purpose of determining styling langauge for
359			an <abbr>HTML</abbr> <code>style</code> element.</li>
360			<li id=css-style-content>Content of an <abbr>HTML</abbr> <code>style</code>
361			element whose content is interpreted as a CSS style sheet
362			<em class=rfc2119>MUST</em> consist of zero or more
363			<a href="http://www.whatwg.org/specs/web-apps/current-work/#text-node">text nodes</a>.
364			Note that it may also contain zero or more comment and/or processing
365			instruction nodes.</li>
366			</ul>
367
368	wakaba	1.11	</div>
369
370	wakaba	1.14	<div class=section id=regexp>
371			<h3>Regular expressions</h3>
372
373			<p>Regular expression defined in ECMAScript Third Edition Section
374			15.10.1 is implemented, with the addition of the support for obsolete
375			octal escape notation commonly supported by Web browsers.
376
377			<p>To identify ECMAScript regular expressions, the Internet Media Type
378			<a
379			href="http://suika.fam.cx/%7Ewakaba/wiki/sw/n/text+x-regexp-js"><code>text/x-regexp-js</code></a>
380			is used.
381
382			</div>
383
384	wakaba	1.11	<div class=section id=webidl>
385	wakaba	1.14	<h3>WebIDL</h3>
386	wakaba	1.11
387			<p><a href="http://dev.w3.org/cvsweb/~checkout~/2006/webapi/WebIDL/Overview.html?rev=1.96&content-type=text/html;%20charset=utf-8">WebIDL
388			Editor's Draft revision 1.96 (<time datetime=2008-09-03>3 September
389			2008</time>)</a> is implemented.</p>
390	wakaba	1.14	</div>
391
392	wakaba	1.1	</div>
393
394			</body>
395			</html>