Bugzilla – Bug 285
Revamp the 'interactive content' definitions so they make sense.
Last modified: 2008-08-18 11:31:38 CEST
Index: source =================================================================== --- source (revision 2017) +++ source (revision 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 |