이 페이지의 이전 버전을 보고 있습니다. 현재 버전 보기.

현재와 비교 페이지 이력 보기

« 이전 버전 17 다음 »

Changes made to element properties by using setProperty() will not be applied.

  • The cause can be found by viewing the error details received. Useful functions ▶ Finding the cause of a W Player API failure

  • When authoring from Web Author, the element names are only unique within the page. If setProperty is used while in Ready state, confirm that the element was selected from within the correct page.
    By using the pageId value that was sent during the state event, you can get the currently running page object returned. Useful functions ▶ $wp.content

  • Among the properties, the name field value is case sensitive.

Remote control or keyboard inputs cannot be sent into web content.

Confirm that a focus is set for the window or document that will use key inputs from the web content.

It is recommended to add a focus code to the Play state stage.

Note

For more information, refer to the details on how to set a focus for a window and document.

https://www.w3schools.com/jsref/met_win_focus.asp

https://www.w3schools.com/jsref/met_html_focus.asp

If you set a focus for multiple web content items, the focus may move to the web content that received Play state, causing an action that does not match the intended action to run. Only set a focus for specific web content that needs a focus.

UDP data cannot be sent.

  • Confirm that the UDP settings configured using Web Author are correct. ▶ Configuring the W Player API settings

  • Confirm that the port number set from Web Author is not used in a different process. If it is used in a different process, change the port and try again.

    Note

    "47475" is the port for W Player playback. Ensure that this port is not used.

Datalink table data cannot be sent.

  • Confirm that the Datalink settings and Datalink Server settings configured using Web Author are correct. ▶ Configuring the W Player API settings

  • Confirm that communication is possible in the network environment for Datalink Server and W Player.

If web content is published using W Player API and played for an extended period of time, issues such as playback performance degradation or Player restart can occur.

Confirm that there is no memory leak in the published web content. To use W Player API, add "$wp = null;" while in Stop state to prevent a memory leak.
(For key functions, refer to the following: ▶ Receiving a state event)

Video is not played properly when using a video tag in web content.

  • Confirm that the video file path is correct. Assets added to web content are saved under the root directory imported through getRootDirectory() API.

  • Confirm that the video format is a format supported by the device on which the video is used. It can be confirmed from the following URL.

    https://developer.samsung.com/smarttv/develop/specifications/media-specifications.html

  • W Player loads two pages to the Back Page layer and Front Page layer, to ensure seamless transition. Confirm that the video fields located in the Back Page layer and Front Page layer do not overlap. If the fields overlap, playback will not work.

  • W Player loads two pages to the Back Page layer and Front Page layer, to ensure seamless transition. Adjust the number of video files located in the Back Page layer and Front Page layer to 3 or less. If the number exceeds 3, playback will not work. If you set the sync timeline option when authoring, which is one of the web content properties, video is only loaded at the Front Page layer (Play stage), allowing playback restrictions to be overridden. Note that flickering may occur during playback at the Play stage. ▶ Configuring the W Player API settings