Rearrange tables so that navigation can be added back to certain pages.

native_client_sdk/doc_generated/devguide/coding/progress-events.html

-{{+bindTo:partials.standard_nacl_api}}
+{{+bindTo:partials.standard_nacl_article}}
 
 <section id="progress-events">
-<h1 id="progress-events">Progress Events</h1>
+<span id="devcycle-progress-events"></span><h1 id="progress-events"><span id="devcycle-progress-events"></span>Progress Events</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#module-loading-and-progress-events" id="id3">Module loading and progress events</a></li>
 <li><a class="reference internal" href="#handling-progress-events" id="id4">Handling progress events</a></li>
 <li><a class="reference internal" href="#displaying-load-status" id="id5">Displaying load status</a></li>
 <li><a class="reference internal" href="#the-lasterror-attribute" id="id6">The <code>lastError</code> attribute</a></li>
 <li><a class="reference internal" href="#the-readystate-attribute" id="id7">The <code>readyState</code> attribute</a></li>
 <li><a class="reference internal" href="#the-exitstatus-attribute" id="id8">The <code>exitStatus</code> attribute</a></li>
 </ul>
 
@@ skipping 12 matching lines @@
 <p>The Native Client runtime reports a set of state changes during the module
 loading process by means of DOM progress events. This set of events is a direct
 port of the proposed W3C <a class="reference external" href="http://www.w3.org/TR/progress-events/">Progress Events</a> standard (except for the <code>crash</code>
 event which is an extension of the W3C standard). The following table lists the
 events types reported by the Native Client runtime:</p>
 <table border="1" class="docutils">
 <colgroup>
 </colgroup>
 <thead valign="bottom">
 <tr class="row-odd"><th class="head">Event</th>
-<th class="head">Description</th>
-<th class="head">Number of
-times
+<th class="head">Times
 triggered</th>
-<th class="head">When event is
+<th class="head">When
 triggered</th>
 <th class="head">How you might
-react to
-event</th>
+respond</th>
 </tr>
 </thead>
 <tbody valign="top">
-<tr class="row-even"><td><code>loadstart</code></td>
-<td>Native Client has
-started to load a
-Native Client
-module.</td>
+<tr class="row-even"><td><dl class="first last docutils">
+<dt><code>loadstart</code></dt>
+<dd>Native Client has started to
+load a Native Client module.</dd>
+</dl>
+</td>
 <td>once</td>
-<td>This is the
+<td>The
 first
 progress
 event
-triggered
 after the
 Native Client
 module is
 instantiated
 and
 initialized.</td>
 <td>Display a
 status
 message, such
 as
 &#8220;Loading...&#8221;</td>
 </tr>
-<tr class="row-odd"><td><code>progress</code></td>
-<td>Part of the module
-has been loaded.</td>
+<tr class="row-odd"><td><dl class="first last docutils">
+<dt><code>progress</code></dt>
+<dd>Part of the module has been
+loaded.</dd>
+</dl>
+</td>
 <td>zero or
 more</td>
 <td>After
 <code>loadstart</code>
 has been
 dispatched.</td>
 <td>Display a
 progress bar.</td>
 </tr>
-<tr class="row-even"><td><code>error</code></td>
-<td>The Native Client
-module failed to
-start execution
-(includes any
-error before or
-during
-initialization of
-the module). The
-<code>lastError</code>
-attribute
-(mentioned later)
-provides details
-on the error
-(initialization
-failed, sel_ldr
-did not start,
-and so on).</td>
+<tr class="row-even"><td><dl class="first last docutils">
+<dt><code>error</code></dt>
+<dd>The Native Client module failed
+to start execution (includes any
+error before or during
+initialization of the module).
+The <code>lastError</code> attribute
+(mentioned later) provides
+details on the error
+(initialization failed, sel_ldr
+did not start, and so on).</dd>
+</dl>
+</td>
 <td>zero or
 once</td>
-<td>After the
-last
+<td>After the last
 <code>progress</code>
-event has
-been
+event has been
 dispatched,
 or after
 <code>loadstart</code>
 if no
 <code>progress</code>
 event was
 dispatched.</td>
 <td>Inform user
 that the
 application
 failed to
 load.</td>
 </tr>
-<tr class="row-odd"><td><code>abort</code></td>
-<td>Loading of the
-Native Client
-module was
-aborted by the
-user.</td>
+<tr class="row-odd"><td><dl class="first last docutils">
+<dt><code>abort</code></dt>
+<dd>Loading of the NativeClient
+module was aborted by the user.</dd>
+</dl>
+</td>
 <td>zero or
 once</td>
-<td>After the
-last
+<td>After the last
 <code>progress</code>
-event has
-been
-dispatched,
-or after
+event has been
+dispatched, or
+after
 <code>loadstart</code>
 if no
 <code>progress</code>
 event was
 dispatched.</td>
 <td>It&#8217;s not
 likely you
-will want to
-respond to
-this event.</td>
+will want to</td>

[mkearney1, 2014/09/12 23:40:34]

Small nit- add period after 'to'.

 </tr>
-<tr class="row-even"><td><code>load</code></td>
-<td>The Native Client
-module was
-successfully
-loaded, and
-execution was
-started. (The
-module was
-initialized
-successfully.)</td>
+<tr class="row-even"><td><dl class="first last docutils">
+<dt><code>load</code></dt>
+<dd>The Native Client module was
+successfully loaded, and
+execution was started.
+(The module was initialized
+successfully.)</dd>
+</dl>
+</td>
 <td>zero or
 once</td>
 <td>After the
 last
 <code>progress</code>
-event has
-been
-dispatched,
-or after
+event has been
+dispatched, or
+after
 <code>loadstart</code>
 if no
 <code>progress</code>
 event was
 dispatched.</td>
 <td>Remove the
 progress bar.</td>
 </tr>
-<tr class="row-odd"><td><code>loadend</code></td>
-<td>Loading of the
-Native Client
-module has
-stopped. Load
-succeeded
-(<code>load</code>),
-failed
-(<code>error</code>), or
-was aborted
-(<code>abort</code>).</td>
+<tr class="row-odd"><td><dl class="first last docutils">
+<dt><code>loadend</code></dt>
+<dd>Loading of the Native Client
+module has stopped. Load
+succeeded (<code>load</code>), failed
+(<code>error</code>), or was aborted
+(<code>abort</code>).</dd>
+</dl>
+</td>
 <td>once</td>
 <td>After an
 <code>error</code>,
 <code>abort</code>, or
 <code>load</code>
 event was
 dispatched.</td>
 <td>Indicate
 loading is
 over
-(regardless
-of failure or
+(regardless of
+failure or
 not).</td>
 </tr>
-<tr class="row-even"><td><code>crash</code></td>
-<td>The Native Client
-module is not
-responding (died
-on an
-<code>assert()</code> or
-<code>exit()</code>) after
-a successful
-load. This event
-is unique to
-Native Client and
-is not part of
-the W3C Progress
-Events standard.
-The <code>exitStatus</code>
-attribute provides
-the numeric exit
-status value.</td>
+<tr class="row-even"><td><dl class="first last docutils">
+<dt><code>crash</code></dt>
+<dd>The Native Client module is not
+responding (died on an
+<code>assert()</code> or <code>exit()</code>)
+after a successful load. This
+event is unique to Native Client
+and is not part of the W3C
+Progress Events standard. The
+<code>exitStatus</code> attribute
+provides the numeric exit
+status.</dd>
+</dl>
+</td>
 <td>zero or
 once</td>
 <td>After a
 <code>loadend</code>.</td>
 <td>Notify user
 that the
 module did
 something
 illegal.</td>
 </tr>
@@ skipping 190 matching lines @@
 <li>In the case of explicit calls to <code>exit(n)</code>, the numeric value will be
 <code>n</code> (between 0 and 255).</li>
 <li>In the case of crashes and calls to <code>abort()</code>, the numeric value will
 be non-zero, but the exact value will depend on the chosen libc and the
 target architecture, and may change in the future. Applications should not
 rely on the <code>exitStatus</code> value being stable in these cases, but the value
 may nevertheless be useful for temporary debugging.</li>
 </ul>
 </section>
 
-{{/partials.standard_nacl_api}}
+{{/partials.standard_nacl_article}}