NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 595 - <object usemap> is interactive. (bug 6790)
<object usemap> is interactive. (bug 6790)
Status: NEW
Product: Validator.nu
Classification: Unclassified
Component: General
HEAD
All All
: P2 normal
Assigned To: Nobody
http://svn.whatwg.org/webapps/source?...
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-14 14:57 CEST by Henri Sivonen
Modified: 2009-11-23 17:17 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henri Sivonen 2009-07-14 14:57:12 CEST
Index: source
===================================================================
--- source	(revision 3161)
+++ source	(revision 3162)
@@ -18568,7 +18568,7 @@
    <dd><span>Flow content</span>.</dd>
    <dd><span>Phrasing content</span>.</dd>
    <dd><span>Embedded content</span>.</dd>
-   <dd>If the element has an <code title="attr-hyperlink-usemap">usemap</code> attribute: <span>Interactive content</span>.</dd>
+   <dd>If the element has a <code title="attr-hyperlink-usemap">usemap</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>
@@ -20758,6 +20758,7 @@
    <dd><span>Phrasing content</span>.</dd>
    <dd><span>Embedded content</span>.</dd>
    <dd><span title="category-listed">Listed</span>,  <span title="category-submit">submittable</span>, <span>form-associated element</span>.</dd>
+   <dd>If the element has a <code title="attr-hyperlink-usemap">usemap</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>
Comment 1 Michael[tm] Smith 2009-07-15 08:16:26 CEST
I believe that no additional v.nu code changes are needed for this; v.nu was already treating object@usemap as an interactive element, it was just that the spec had not explicitly included it as such until r3162