[e] (0) Cleanup some more XXX issues that I decided to punt on.

git-svn-id: http://svn.whatwg.org/webapps@4056 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Sep 29, 2009 · 45bb143 · 45bb143
1 parent aed122a
commit 45bb143
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 29 deletions.
diff --git a/index b/index
@@ -10528,8 +10528,9 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p&gt;
   document to other resources.</p>
 
   <p>The destination of the link(s) is given by the <dfn id=attr-link-href title=attr-link-href><code>href</code></dfn> attribute, which must
-  be present and must contain a <a href=#valid-url>valid URL</a>. If the <code title=attr-link-href><a href=#attr-link-href>href</a></code> attribute is absent, then the
-  element does not define a link.</p>
+  be present and must contain a <a href=#valid-url>valid URL</a>. <span class=impl>If the <code title=attr-link-href><a href=#attr-link-href>href</a></code>
+  attribute is absent, then the element does not define a
+  link.</span></p>
 
   <p>The types of link indicated (the relationships) are given by the
   value of the <dfn id=attr-link-rel title=attr-link-rel><code>rel</code></dfn>
@@ -77164,16 +77165,6 @@ interface <a href=#htmldocument>HTMLDocument</a> {
 TODO:
  XXX * need to become consistent about whether or not to quote keyword
        ("<code title="">foo</code>" vs <code>foo</code>)
- XXX * onclick="" only fires if it is a MouseEvent ?
- XXX * hsivonen makes the following suggestions:
-       > To make document conformance a more useful concept for the purpose of catching
-       > author errors, I suggest that the following attributes be made required:
-       > href and rel on link
-       > href on base
-       > name and content on meta (other than the encoding decl)
-       > src on img
-       > code, height and width on applet
-       > name and value on param
  XXX * make the spec consistent about whether the word "algorithm" is part of
        an algorithm's name or not ("</dfn> algorithm", "</span> algorithm")
  XXX * make a consistent decision of which of the following formats to use:
@@ -77200,14 +77191,12 @@ TODO:
          0x12 ("<code title="">foo</code>")
          0x12 ('<code title="">foo</code>')
  XXX * check case of hex characters in the ASCII cases.
- XXX * option.text should do the same as option.textContent
  XXX * use the sample widgets:
           <li><img alt="A text field with editable sections for each
           value, with a button to pop up a dialog showing a calendar or
           clock." src="sample-datetime-ui-2"></li>
           <li><img alt="A calendar grid with a clock in the upper right
           hand corner." src="sample-datetime-ui-3"></li>
- XXX * should "mixed fractional number" be used instead of "fractional"?
  XXX * make the spec more consistent about its use of "hexadecimal"
        and "base-sixteen", the order that 0-9 A-Z a-z is mentioned,
        and the detail to which the spec explains how to interpret a

diff --git a/source b/source
@@ -10998,9 +10998,10 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
 
   <p>The destination of the link(s) is given by the <dfn
   title="attr-link-href"><code>href</code></dfn> attribute, which must
-  be present and must contain a <span>valid URL</span>. If the <code
-  title="attr-link-href">href</code> attribute is absent, then the
-  element does not define a link.</p>
+  be present and must contain a <span>valid URL</span>. <span
+  class="impl">If the <code title="attr-link-href">href</code>
+  attribute is absent, then the element does not define a
+  link.</span></p>
 
   <p>The types of link indicated (the relationships) are given by the
   value of the <dfn title="attr-link-rel"><code>rel</code></dfn>
@@ -91494,16 +91495,6 @@ interface <span>HTMLDocument</span> {
 TODO:
  XXX * need to become consistent about whether or not to quote keyword
        ("<code title="">foo</code>" vs <code>foo</code>)
- XXX * onclick="" only fires if it is a MouseEvent ?
- XXX * hsivonen makes the following suggestions:
-       > To make document conformance a more useful concept for the purpose of catching
-       > author errors, I suggest that the following attributes be made required:
-       > href and rel on link
-       > href on base
-       > name and content on meta (other than the encoding decl)
-       > src on img
-       > code, height and width on applet
-       > name and value on param
  XXX * make the spec consistent about whether the word "algorithm" is part of
        an algorithm's name or not ("</dfn> algorithm", "</span> algorithm")
  XXX * make a consistent decision of which of the following formats to use:
@@ -91530,14 +91521,12 @@ TODO:
          0x12 ("<code title="">foo</code>")
          0x12 ('<code title="">foo</code>')
  XXX * check case of hex characters in the ASCII cases.
- XXX * option.text should do the same as option.textContent
  XXX * use the sample widgets:
           <li><img alt="A text field with editable sections for each
           value, with a button to pop up a dialog showing a calendar or
           clock." src="sample-datetime-ui-2"></li>
           <li><img alt="A calendar grid with a clock in the upper right
           hand corner." src="sample-datetime-ui-3"></li>
- XXX * should "mixed fractional number" be used instead of "fractional"?
  XXX * make the spec more consistent about its use of "hexadecimal"
        and "base-sixteen", the order that 0-9 A-Z a-z is mentioned,
        and the detail to which the spec explains how to interpret a