Hi Tim

I have run into a (well documented) issue when trying to play videos whose content is being returned from a standard REST API. This works on all browsers except Safari on macOS and iOS. The reason is because the content link returned by the REST API will not include a file extension. It will look something like this:

api/v1/Documents/5/Contents

Safari need to be "told" what type the content is, whereas Chrome et al do not. Furthermore, Safari has to be told via the use of a nested source element, like this:

<video>
 <source src="api/v1/Documents/5/Contents" type="video/mp4">
</video>

It is not sufficient to add the "type=" inside the video element. It has to be within a "source" child.

I had thought that I might be able to get around this by jiggling with the video element that you're creating behind the scenes but I'm struggling to locate it, let along modify it!

Can you point me in the right direction please?

Thanks
Mark

Mark,

<< It is not sufficient to add the "type=" inside the video element. It has to be within a "source" child.

I had thought that I might be able to get around this by jiggling with the video element that you're creating behind the scenes but I'm struggling to locate it, let along modify it!

Can you point me in the right direction please? >>

What you want is the TMediaElement in the WebUI unit.

I need to see about changing the media elements (audio, video, and image) to support multiple sources.  This will also allow one to specify the MIME type.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

>>I need to see about changing the media elements (audio, video, and image) to support multiple sources.  This will >>also allow one to specify the MIME type.

That would fix my issue and also provide a nice "fallback". Perfect result.