html5/spec-author-view/multipage spec.html,1.3,1.4

Update of /sources/public/html5/spec-author-view/multipage
In directory hutz:/tmp/cvs-serv25578/multipage

Modified Files:
	spec.html 
Log Message:
Clarify text that some people thought implied you had to implement aliases for encodings you didn't support (whatever that would mean). (whatwg r3682)

[updated by splitter]


Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/multipage/spec.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- spec.html	27 Aug 2009 07:56:37 -0000	1.3
+++ spec.html	27 Aug 2009 07:58:24 -0000	1.4
@@ -0,0 +1,26816 @@
+<!DOCTYPE html><!-- when publishing, change bits marked ZZZ --><html lang=en-US-x-Hixie><head><title>HTML 5</title><style type=text/css>
+   pre { margin-left: 2em; white-space: pre-wrap; }
+   h2 { margin: 3em 0 1em 0; }
+   h3 { margin: 2.5em 0 1em 0; }
+   h4 { margin: 2.5em 0 0.75em 0; }
+   h5, h6 { margin: 2.5em 0 1em; }
+   h1 + h2, h1 + h2 + h2 { margin: 0.75em 0 0.75em; }
+   h2 + h3, h3 + h4, h4 + h5, h5 + h6 { margin-top: 0.5em; }
+   p { margin: 1em 0; }
+   hr:not(.top) { display: block; background: none; border: none; padding: 0; margin: 2em 0; height: auto; }
+   dl, dd { margin-top: 0; margin-bottom: 0; }
[...26786 lines suppressed...]
+       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
+       string as a hexadecimal number.
+ XXX * expose the form data set, either as an object (on which one can
+       invoke the JSON serialiser), or in the form of a method on
+       HTMLFormElement that returns the form data set serialised
+       according to a particular encoding (defaulting to the form's
+       enctype="" one, probably). This would allow forms to be used
+       with XHR-like systems without having to manually construct the
+       form data set the way that is done today.
+ XXX * become more consistent about what markup we use to mark up
+       productions (nothing? <i>? <code>?)
+ XXX * should check all cases of 'active document' and change the
+       relevant ones to 'fully active document'.
+ XXX * use <code>Document</code> consistently instead of 'document'.
+ XXX * s/raise/throw/g
+ XXX * be clearer about arrays/lists/collections being zero-based
+       despite using the term "/index/th".
+--></body></html>
\ No newline at end of file

Received on Thursday, 27 August 2009 07:58:35 UTC