When an HTML5 application is loaded on an x86 media player, it is run within a built-in web browser that has been modified to play back HTML applications in a digital signage environment. 

When the application is rendered on the player only the document area is displayed. There are no windows, navigation buttons, URL bar, status bar or other GUI elements visible. The display is similar to using an iframe where the HTML document area is the only thing visible.

It is highly suggested to run firmware R8.9 or greater on the media player in order to take advantage of the newer version of the built-in Blink (Chromium) browser engine that supports most HTML5 features and remote debugging capabilities.

Firmware R8.8 or less will render HTML content using the WebKit browser engine by default. 

Firmware R8.9 or greater will render HTML content using the Blink (Chromium) version 43 browser by default. 

Disabling the Chromium Browser

The Chromium browser is enabled by default on the R8.9+ firmware however, if there is a need to use the WebKit browser, Chromium can be disabled. This setting will be ignored by media players running R8.8 or less firmware.

  • Create an attribute set with the name: EnGage
    • Create an attribute with the name: UseChromium
      • Type: Boolean
      • Player Variable Mode: Server Set
    • Create an attribute with the name: ChromiumDebuggingPortSetting a value <= 0, will disable debugging. If you leave this field empty, it defaults to 0.
      • Type: Integer
      • Player Variable Mode: Server Set
  • Navigate to the Site->Attributes tab on the site that will be running the HTML application
  • Assign the EnGage attribute set
  • Set the value of the UseChromium to "No"
  • If debugging is required on development player, set the value of ChromiumDebuggingPort to 9222. Otherwise the default value of 0 should be used.
  • Navigate to the Site->Assignments tab
  • Publish the "Player Variables" entity.
    • Viewing the Player Variables entity will display the currently set Player variables for the site
  • Reboot the media player.

Enabling the Chromium browser applies to both the HTML5 widget and URL widget.

Document / Zone Size / Scroll Bars

When an HTML5 application is deployed to a Media Player, a browser window is created within the programmed Layout Zone to contain the application. As a result, the document size will be determined by the size of the zone. A layout may be created with multiple layout zones, each of a different size. The HTML5 application may be deployed into a zone with a size of 1280x720, or into a "banner" sized zone of 1280x100. Thus care should be taken in the design of the application. An application can be either a fixed size, or, ideally implemented using responsive design techniques to automatically alter the elements within the application to fit various aspect ratios and resolutions depending on the document size. Responsive design techniques may require more upfront development as compared to designing an application for a specific resolution or aspect ratio.

The browser's scroll bars will become visible if the elements are larger than document size. CSS can be used to hide the scroll bars.

An example multi-zone program with an HTML widget in the main zone. The document size will be determined by the zone dimensions in which the HTML5 widget is set to playback.