The sequence of events for a successful module load is as follows:Įrrors that occur during loading are logged to the JavaScript console in Google Chrome (select the menu icon > Tools > JavaScript console). Notify user that the module did something illegal. The exitStatus attribute provides the numeric exit status. This event is unique to Native Client and is not part of the W3C Progress Events standard. Indicate loading is over (regardless of failure or not).Ĭrash The Native Client module is not responding (died on an assert() or exit()) after a successful load. Load succeeded ( load), failed ( error), or was aborted ( abort).Īfter an error, abort, or load event was dispatched. Loadend Loading of the Native Client module has stopped. (The module was initialized successfully.)

Load The Native Client module was successfully loaded, and execution was started.

It’s not likely you will want to respond to this event. Inform user that the application failed to load.Ībort Loading of the NativeClient module was aborted by the user. The lastError attribute (mentioned later) provides details on the error (initialization failed, sel_ldr did not start, and so on).Īfter the last progress event has been dispatched, or after loadstart if no progress event was dispatched. Progress Part of the module has been loaded.Įrror The Native Client module failed to start execution (includes any error before or during initialization of the module). The first progress event after the Native Client module is instantiated and initialized.ĭisplay a status message, such as “Loading.” Loadstart Native Client has started to load a Native Client module. The following table lists the events types reported by the Native Client runtime: This set of events is a direct port of the proposed W3C Progress Events standard (except for the crash event which is an extension of the W3C standard). The Native Client runtime reports a set of state changes during the module loading process by means of DOM progress events. You can find this code in the /pepper_/examples/tutorial/load_progress/ directory in the Native Client SDK download. The load_progress example illustrates progress event handling. This section assumes you are familiar with the material presented in the Technical Overview. This section describes how to monitor progress events (events that occur during the loading and execution of a Native Client module). There are five types of events that developers can respond to in Native Client: progress, message, view change, focus, and input events (each described in the glossary below).

Progress developer studio download