html5/spec Overview.html,1.3217,1.3218

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv31253

Modified Files:
	Overview.html 
Log Message:
Cleanup some more XXX issues that I decided to punt on. (whatwg r4056)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3217
retrieving revision 1.3218
diff -u -d -r1.3217 -r1.3218
--- Overview.html	29 Sep 2009 11:27:18 -0000	1.3217
+++ Overview.html	29 Sep 2009 11:32:25 -0000	1.3218
@@ -9362,8 +9362,9 @@
    </dd>
   </dl><p>The <code><a href="#the-link-element">link</a></code> element allows authors to link their
   document to other resources.<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>The types of link indicated (the relationships) are given by the
+  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>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>
   attribute, which must be present, and must have a value that is a
   <a href="#set-of-space-separated-tokens">set of space-separated tokens</a>. The <a href="#linkTypes">allowed values and their meanings</a> are defined
@@ -70566,16 +70567,6 @@
 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:
@@ -70602,14 +70593,12 @@
          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

Received on Tuesday, 29 September 2009 11:32:38 UTC