# View video file in ui

**URL:** <https://discourse.nodered.org/t/view-video-file-in-ui/5240>\
**Category:** Dashboard\
**Created:** [27 November 2018 15:54 UTC](https://discourse.nodered.org/t/view-video-file-in-ui/5240 "2018-11-27T15:54:15Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [1 December 2018 14:10 UTC](https://discourse.nodered.org/t/view-video-file-in-ui/5240/7 "2018-12-01T14:10:44Z")

</div>

Hi @hugobox,

Thanks for the tip!!!  
I tried something similar yesterday, but then I also arrived in the catch part...

To be sure, I have reset again my autoplay policy to the default:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/8/86896985bbd53e026b05bd8369265a700dc02957.png)

Then both your and mine version still work fine. Very weird!

Afterwards I have asked Chrome to make sure that a user gesture is required, before start playing:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/9/9465cfeefd2bb3fc1b08362311f71af5971a6e87.png)

Then both versions still work fine. I don't get it anymore 🥴

Other nodes are also being fixed for the policy changes (see [discussion](https://discourse.nodered.org/t/audio-context-changes/250) and corresponding [pull request](https://github.com/lorentzlasson/node-red-contrib-play-audio/pull/9)), but I don't get how they can get around the user gestures that way ...

P.S. But your version is anyway better than mine ...  
Bart

---

_[View the full topic](https://discourse.nodered.org/t/view-video-file-in-ui/5240)._
