Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(158)

Side by Side Diff: native_client_sdk/doc_generated/devguide/coding/progress-events.html

Issue 2875303003: Add migration to WebAssembly information to PNaCl / NaCl docs. (Closed)
Patch Set: fix Created 3 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 {{+bindTo:partials.standard_nacl_article}} 1 {{+bindTo:partials.standard_nacl_article}}
2 2
3 <section id="progress-events"> 3 <b><font color="#cc0000">
4 <span id="devcycle-progress-events"></span><h1 id="progress-events"><span id="de vcycle-progress-events"></span>Progress Events</h1> 4 NOTE:
5 Deprecation of the technologies described here has been announced
6 for platforms other than ChromeOS.<br/>
7 Please visit our
8 <a href="/native-client/migration">migration guide</a>
9 for details.
10 </font></b>
11 <hr/><section id="progress-events">
12 <h1 id="progress-events">Progress Events</h1>
5 <div class="contents local" id="contents" style="display: none"> 13 <div class="contents local" id="contents" style="display: none">
6 <ul class="small-gap"> 14 <ul class="small-gap">
7 <li><a class="reference internal" href="#module-loading-and-progress-events" id= "id3">Module loading and progress events</a></li> 15 <li><a class="reference internal" href="#module-loading-and-progress-events" id= "id3">Module loading and progress events</a></li>
8 <li><a class="reference internal" href="#handling-progress-events" id="id4">Hand ling progress events</a></li> 16 <li><a class="reference internal" href="#handling-progress-events" id="id4">Hand ling progress events</a></li>
9 <li><a class="reference internal" href="#displaying-load-status" id="id5">Displa ying load status</a></li> 17 <li><a class="reference internal" href="#displaying-load-status" id="id5">Displa ying load status</a></li>
10 <li><a class="reference internal" href="#the-lasterror-attribute" id="id6">The < code>lastError</code> attribute</a></li> 18 <li><a class="reference internal" href="#the-lasterror-attribute" id="id6">The < code>lastError</code> attribute</a></li>
11 <li><a class="reference internal" href="#the-readystate-attribute" id="id7">The <code>readyState</code> attribute</a></li> 19 <li><a class="reference internal" href="#the-readystate-attribute" id="id7">The <code>readyState</code> attribute</a></li>
12 <li><a class="reference internal" href="#the-exitstatus-attribute" id="id8">The <code>exitStatus</code> attribute</a></li> 20 <li><a class="reference internal" href="#the-exitstatus-attribute" id="id8">The <code>exitStatus</code> attribute</a></li>
13 </ul> 21 </ul>
14 22
(...skipping 387 matching lines...) Expand 10 before | Expand all | Expand 10 after
402 <code>n</code> (between 0 and 255).</li> 410 <code>n</code> (between 0 and 255).</li>
403 <li>In the case of crashes and calls to <code>abort()</code>, the numeric value will 411 <li>In the case of crashes and calls to <code>abort()</code>, the numeric value will
404 be non-zero, but the exact value will depend on the chosen libc and the 412 be non-zero, but the exact value will depend on the chosen libc and the
405 target architecture, and may change in the future. Applications should not 413 target architecture, and may change in the future. Applications should not
406 rely on the <code>exitStatus</code> value being stable in these cases, but the v alue 414 rely on the <code>exitStatus</code> value being stable in these cases, but the v alue
407 may nevertheless be useful for temporary debugging.</li> 415 may nevertheless be useful for temporary debugging.</li>
408 </ul> 416 </ul>
409 </section> 417 </section>
410 418
411 {{/partials.standard_nacl_article}} 419 {{/partials.standard_nacl_article}}
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698