The Player page Player.html
is fairly simplistic, extracting a video path from the query string in order to pass into this statement
However, if the video is an MP4 (for example) rather than being HLS, the player will instantiate and then that browser tab will become unresponsive in Chromium.
This is because the embed script assumes HLS by default, and so will have written a source
tag in with the type
attribute set to application/x-mpegURL
The player then tries to parse the blob as if it were a manifest.