Basic structure of web content elements
ContentApi
Modify or import pages in LFD content and image, text, and/or video element properties included in the pages.
LocalApi
Import information about the local environment in which web content elements are run.
DeviceApi
Import information related to devices such as W Player and Tizen.
UtilityApi
Access utilities required for developing web content elements.
Event CallBack
Provides a callback function that receives life cycle events of web content elements and data sent from datalink and/or external sources.
Life cycle of web content elements
Web content elements have the following life cycle, and the time at which an element goes into each state can be received via the callback function. Seamless playback is possible by using Ready and Play states.
Ready
Sends the time at which web content elements can use W Player API after all elements in a page are loaded. A web content element is loaded in iframe format, being in the Back Page layer which is a state in which the element is not displayed yet (and the previous content is playing on the current screen). Reset is possible as required, before the element appears on the screen.
Play
Sends the time at which the web content element appears on the screen (Front Page layer).
- Page Changed: Sends the time at which page transition takes place during playback. (This only works when the web content belongs to the common page.)
- When authoring from Web Author, set the "Sync Timeline" option to allow load and playback to take place in sequential order as soon as the content element appears on the screen (Play state). After the element appears on the screen, the Ready, Play, and Stop states will be sent. (Note that flickering may occur during loading.)
Stop
Sends the time before which web content element playback ends. Resources used in the web content element can be returned. (e.g., clearInterval, clearTimeout, $wp = null)
Caution
A memory leak in a resource that has not been returned properly may affect W Player playback.