[html5] r2018 - [ac] (0) Revamp the 'interactive content' definitions so they make sense.
whatwg at whatwg.org
whatwg at whatwg.org
Tue Aug 5 14:17:18 PDT 2008
Author: ianh
Date: 2008-08-05 14:17:18 -0700 (Tue, 05 Aug 2008)
New Revision: 2018
Modified:
index
source
Log:
[ac] (0) Revamp the 'interactive content' definitions so they make sense.
Modified: index
===================================================================
--- index 2008-08-05 21:09:44 UTC (rev 2017)
+++ index 2008-08-05 21:17:18 UTC (rev 2018)
@@ -17654,6 +17654,10 @@
<dd><a href="#embedded1">Embedded content</a>.
+ <dd>If the element has a <code title=attr-media-controls><a
+ href="#controls">controls</a></code> attribute: <a
+ href="#interactive1">Interactive content</a>.
+
<dt>Contexts in which this element may be used:
<dd>Where <a href="#embedded1">embedded content</a> is expected.
@@ -17991,6 +17995,10 @@
<dd><a href="#embedded1">Embedded content</a>.
+ <dd>If the element has a <code title=attr-media-controls><a
+ href="#controls">controls</a></code> attribute: <a
+ href="#interactive1">Interactive content</a>.
+
<dt>Contexts in which this element may be used:
<dd>Where <a href="#embedded1">embedded content</a> is expected.
@@ -26718,6 +26726,8 @@
<dd><a href="#flow-content0">Flow content</a>.
+ <dd><a href="#interactive1">Interactive content</a>.
+
<dt>Contexts in which this element may be used:
<dd>Where <a href="#flow-content0">flow content</a> is expected.
@@ -26850,13 +26860,6 @@
enter key, etc).</p>
<!-- XXXPA -->
- <p class=big-issue>This element is defined as interactive, which means it
- can't contain other interactive elements, despite the fact that we expect
- it to work with other interactive elements e.g. checkboxes and input
- fields. It should be called something like a Leaf Interactive Element or
- something, which counts for ancestors looking in and not descendants
- looking out.
-
<p>The <code><a href="#datagrid0">datagrid</a></code> element represents an
interactive representation of tree, list, or tabular data.
@@ -29088,9 +29091,10 @@
<dd>Where <a href="#phrasing0">phrasing content</a> is expected.
- <dt><a href="#phrasing0">Phrasing content</a>.
+ <dt>Content model:
- <dd>Empty.
+ <dd><a href="#phrasing0">Phrasing content</a>, but there must be no <a
+ href="#interactive1">interactive content</a> descendant.
<dt>Element-specific attributes:
@@ -29277,6 +29281,11 @@
<dd><a href="#flow-content0">Flow content</a>.
+ <dd>If the element's <code title=attr-menu-type><a
+ href="#type17">type</a></code> attribute is in the <a href="#tool-bar"
+ title="tool bar state">tool bar</a> state: <a
+ href="#interactive1">Interactive content</a>.
+
<dd>If there is a <code><a href="#menu">menu</a></code> element ancestor:
<a href="#phrasing0">phrasing content</a>.
@@ -55578,9 +55587,6 @@
http://www.aujsproduction.com/samples/wishlist/revampedselector.asp
-interactive elements can't be nested (as in <a><button><input></button></a>)
-
-
need a summary of all the content models and how they interact:
a | interactive strictly inline-level element | where inline-level content is expected | strictly inline-level content | interactive elements must not be nested
i | strictly inline-level element | where inline-level content is expected | strictly inline-level content |
Modified: source
===================================================================
--- source 2008-08-05 21:09:44 UTC (rev 2017)
+++ source 2008-08-05 21:17:18 UTC (rev 2018)
@@ -15203,6 +15203,7 @@
<dl class="element">
<dt>Categories</dt>
<dd><span>Embedded content</span>.</dd>
+ <dd>If the element has a <code title="attr-media-controls">controls</code> attribute: <span>Interactive content</span>.</dd>
<dt>Contexts in which this element may be used:</dt>
<dd>Where <span>embedded content</span> is expected.</dd>
<dt>Content model:</dt>
@@ -15523,6 +15524,7 @@
<dl class="element">
<dt>Categories</dt>
<dd><span>Embedded content</span>.</dd>
+ <dd>If the element has a <code title="attr-media-controls">controls</code> attribute: <span>Interactive content</span>.</dd>
<dt>Contexts in which this element may be used:</dt>
<dd>Where <span>embedded content</span> is expected.</dd>
<dt>Content model:</dt>
@@ -24094,6 +24096,7 @@
<dl class="element">
<dt>Categories</dt>
<dd><span>Flow content</span>.</dd>
+ <dd><span>Interactive content</span>.</dd>
<dt>Contexts in which this element may be used:</dt>
<dd>Where <span>flow content</span> is expected.</dd>
<dt>Content model:</dt>
@@ -24198,13 +24201,6 @@
detect when a row/selection has been deleted, activated, etc, by the
user (delete key, enter key, etc).</p> <!-- XXXPA -->
- <p class="big-issue">This element is defined as interactive, which
- means it can't contain other interactive elements, despite the fact
- that we expect it to work with other interactive elements e.g.
- checkboxes and input fields. It should be called something like a
- Leaf Interactive Element or something, which counts for ancestors
- looking in and not descendants looking out.</p>
-
<p>The <code>datagrid</code> element represents an interactive
representation of tree, list, or tabular data.</p>
@@ -26324,8 +26320,8 @@
<dd><span>Interactive content</span>.</dd>
<dt>Contexts in which this element may be used:</dt>
<dd>Where <span>phrasing content</span> is expected.</dd>
- <dt><span>Phrasing content</span>.</dt>
- <dd>Empty.</dd>
+ <dt>Content model:</dt>
+ <dd><span>Phrasing content</span>, but there must be no <span>interactive content</span> descendant.</dd>
<dt>Element-specific attributes:</dt>
<dd><code title="attr-command-type">type</code></dd>
<dt>DOM interface:</dt>
@@ -26503,6 +26499,7 @@
<dl class="element">
<dt>Categories</dt>
<dd><span>Flow content</span>.</dd>
+ <dd>If the element's <code title="attr-menu-type">type</code> attribute is in the <span title="tool bar state">tool bar</span> state: <span>Interactive content</span>.</dd>
<dd>If there is a <code>menu</code> element ancestor: <span>phrasing content</span>.</dd>
<dt>Contexts in which this element may be used:</dt>
<dd>Where <span>flow content</span> is expected.</dd>
@@ -50483,9 +50480,6 @@
http://www.aujsproduction.com/samples/wishlist/revampedselector.asp
-interactive elements can't be nested (as in <a><button><input></button></a>)
-
-
need a summary of all the content models and how they interact:
a | interactive strictly inline-level element | where inline-level content is expected | strictly inline-level content | interactive elements must not be nested
i | strictly inline-level element | where inline-level content is expected | strictly inline-level content |
More information about the Commit-Watchers
mailing list