W3C home > Mailing lists > Public > public-html-diffs@w3.org > January 2009

spec/Overview.html 1.1890 2720 Make outerHTML and insertAdjacentHTML wo

From: poot <cvsmail@w3.org>
Date: Thu, 29 Jan 2009 14:16:31 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090129051632.0855B2BC04@toro.w3.mag.keio.ac.jp>

Make outerHTML and insertAdjacentHTML work on XML too. Reorganise things
and define the interaction of XML and the DOM for the purposes of HTML
APIs. (whatwg r2720)

MediaModeAbstractView
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#mediamodeabstractview
Status of this document
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#status-of-this-document
12.1 Localization
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#localization
12.2 Declarative 2D vector graphics and animation
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#declarative-2d-vector-graphics-and-animation
A vocabulary and associated APIs for HTML and XHTML
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#a-vocabulary-and-associated-apis-for-html-and-xhtml
WindowTimers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#windowtimers
12.3 Declarative 3D scenes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#declarative-3d-scenes
12.4 Timers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#timers
Editor's Draft 29 January 2009
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#editor-s-draft-date-zzz-9-june-2008
12.5 Rendering and the DOM
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#rendering-and-the-dom
clearInterval()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1890.html#dom-windowtimers-clearinterval

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1889&r2=1.1890&f=h
http://html5.org/tools/web-apps-tracker?from=2719&to=2720

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1889
retrieving revision 1.1890
diff -u -d -r1.1889 -r1.1890
--- Overview.html	28 Jan 2009 07:49:12 -0000	1.1889
+++ Overview.html	29 Jan 2009 05:12:42 -0000	1.1890
@@ -8,7 +8,7 @@
    <p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
    <h1>HTML 5</h1>
    <h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->28 January 2009</h2>
+   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->29 January 2009</h2>
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
     <dd><a href="http://www.w3.org/TR/2009/WD-html5-20090610/">http://www.w3.org/TR/2009/WD-html5-20090610/</a></dd>
@@ -97,7 +97,7 @@
   specification's progress along the W3C Recommendation
   track.
[...1168 lines suppressed...]
+  the more common requests.<h3 id=localization><span class=secno>12.1 </span>Localization</h3><p>If you wish to create localized versions of an HTML application,
   the best solution is to preprocess the files on the server, and then
-  use HTTP content negotiation to serve the appropriate language.</p><!-- <p>XXX example here</p> --><!--XXXSVG (remove next section)--><h3 id=declarative-2d-vector-graphics-and-animation><span class=secno>11.2 </span>Declarative 2D vector graphics and animation</h3><p>Embedding vector graphics into XHTML documents is the domain of
-  SVG.</p><!-- <p>XXX example here</p> --><h3 id=declarative-3d-scenes><span class=secno>11.3 </span>Declarative 3D scenes</h3><p>Embedding 3D imagery into XHTML documents is the domain of X3D,
-  or technologies based on X3D that are namespace-aware.</p><!-- <p>XXX example here</p> --><h3 id=timers><span class=secno>11.4 </span>Timers</h3><p class=XXX>This section is expected to be moved to its own
+  use HTTP content negotiation to serve the appropriate language.</p><!-- <p>XXX example here</p> --><!--XXXSVG (remove next section)--><h3 id=declarative-2d-vector-graphics-and-animation><span class=secno>12.2 </span>Declarative 2D vector graphics and animation</h3><p>Embedding vector graphics into XHTML documents is the domain of
+  SVG.</p><!-- <p>XXX example here</p> --><h3 id=declarative-3d-scenes><span class=secno>12.3 </span>Declarative 3D scenes</h3><p>Embedding 3D imagery into XHTML documents is the domain of X3D,
+  or technologies based on X3D that are namespace-aware.</p><!-- <p>XXX example here</p> --><h3 id=timers><span class=secno>12.4 </span>Timers</h3><p class=XXX>This section is expected to be moved to its own
   specification in due course. It needs a lot of work to actually make
   it into a semi-decent spec.<p>Objects that implement the <code><a href=#window>Window</a></code> interface must
   also implement the <code><a href=#windowtimers>WindowTimers</a></code> interface:<pre class=idl>[NoInterfaceObject, ImplementedOn=<a href=#window>Window</a>] interface <dfn id=windowtimers>WindowTimers</dfn> {
@@ -46134,7 +46107,7 @@
   interval, the methods must return without doing anything.<p>For both <code title=dom-windowtimers-setTimeout><a href=#dom-windowtimers-settimeout>setTimeout()</a></code> and <code title=dom-windowtimers-setInterval><a href=#dom-windowtimers-setinterval>setInterval()</a></code>, the clock
   upon which the timers are based must only tick while the
   <a href=#script-group>script group</a> of their callbacks is not
-  <i>frozen</i>.<h3 id=rendering-and-the-dom><span class=secno>11.5 </span>Rendering and the DOM</h3><p class=XXX>This section is expected to be moved to its own
+  <i>frozen</i>.<h3 id=rendering-and-the-dom><span class=secno>12.5 </span>Rendering and the DOM</h3><p class=XXX>This section is expected to be moved to its own
   specification in due course. It needs a lot of work to actually make
   it into a semi-decent spec.<p>Any object implement the <code>AbstractView</code> interface must
   also implement the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface.<pre class=idl>[NoInterfaceObject, ImplementedOn=<span>AbstractView</span>] interface <dfn id=mediamodeabstractview>MediaModeAbstractView</dfn> {
Received on Thursday, 29 January 2009 05:17:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:57 GMT