The Web Page app lets you embed a web page in your Playr page. This web page will always be retrieved directly from the device on which the Playr page is shown. So this also enables you to show web pages that are only accessible from within your own (company) network.
You can configure the app using the following properties:
|Web address||The web address (URL) of the web page to be shown.|
|Zoom||Zoom in or out on the web page.|
|Web page width||Sets the outline width of the web page. Most web pages will adjust their layout to this width.|
|Web page height||Sets the outline height of the web page.|
|Refresh content||Select how often you like the web page to be reloaded during playback. A reload will always be more or less noticeable on the screen during playback. So if you don't expect frequent updates of the web page, be sure set this to a greater refresh interval.|
|Automatically scroll content||Select if you want the content of the web page to scroll up during playback so the content of the whole page is shown. The page will scroll from the position you choose to the "end" set by the Web page height setting. So make sure that that value is large enough for the relevant parts of the page to be shown while scrolling.|
In addition, when you select the Web Page element, it will show vertical and horizontal scroll bars with which you can position the web page within the app such that it only displays the part that you like.
Note that browsers do not always display web pages exactly the same. We therefore recommend to use the same browser for configuring the Web page app in your Playr page as you use for playing your channel. For all apps (ChromeOS, Android and Porteus Kiosk) this is Google Chrome.
Some web pages vertically center their content, like a Google Presentation or a Microsoft Office365 Powerpoint presentation. If you leave the web page height set to the default value of 3000, that content will be invisible at first. Be sure to reduce the web page height to match the actual height of the app to see that content.
And finally there are a number of generic app properties that you can configure that you'll find on many other elements as well.
Security on the internet is an ever present concern and browser manufacturers constantly add new restrictions to ensure maximum security while the user browses the internet. This unfortunately also makes it ever harder to include one web page in another; in this case in a Playr page. We'll address the most common restrictions that you might run into with the Web Page app.
Website owners have the ability to prevent their site from being embedded in another web page. In that case Playr is also unable to display that web page and the app will remain blank. If you yourself are owner of that specific website, then make sure that on your web server, the following is configured:
Content-Security-Policyshould either not be set or at least be set to
frame-ancestors 'self' http://playr.biz http://*.playr.biz https://playr.biz https://*.playr.biz.
X-Frame-Optionsshould not be set. Note that setting the
ALLOW-FROMoption will not work, as documented by Mozilla.
SameSite=None; Securesetting to allow cookies to function within another web page like Playr. It is therefore important to always play Playr in HTTPS. You can force that by checking the Enforce playback via HTTPS setting in the company settings page.
Some websites will show a cookie warning. There are two ways to deal with this:
Showing the content of a website that requires you to log in is practically only possible if you can select to stay logged in forever on that site. In that case, you must first log in to the relevant website from the playback device, indicating that you want to stay logged in forever. To do this, follow the exact same procedure as described above for accepting cookies on your playback device.