Better support for html5 video/audio attributes
we had some trouble with the videoplayer in 7.6. (Standard Media / HTML5) We can't use the "loop" attribute, because of there is no support in the backend.
On base of 8.4dev-master i wrote a little patch which could maybe used for a correct fix. (The patch fixes small typos in tests, too)
You decide that there is only one possibillity for a source tag in a video or an audio tag. Maybe this is incorrect, too? Or an political decision.
#1 Updated by Frans Saris about 2 years ago
- Status changed from New to Needs Feedback
We left out the loop, mute, controls, etc options as these are not all supported by the current 3 video integrations (YouTube, Vimeo and html5). Also it's rather easy to add these options by some additional TCA in a own extension.
The html embed version has only one source because you can only add 1 file so other sources aren't know in the renderer.
#2 Updated by Guido S. about 2 years ago
thanks for your feedback. But i think we should split the standard and the external videos. So i added a second patch which has two new "Filetypes" to split video, youtube and vimeo. With this requirement I can decide to create a different TCA for different cases. Example is given in this patch.
Maybe we can rethink the situation? ;-) (For more discussion you can reach me in slack @ayacoo)
#3 Updated by Frans Saris about 2 years ago
Creating a new file type for every possible video type will not work and isn't extendable by extensions.
These types are also similar with the types used by DAM systems etc.
What could be a solution is showing pallet elements by file extension. Maybe you could look into that.
#4 Updated by Frans Saris about 2 years ago
This goes a little further than your suggestion but could maybe give you some ideas on how to proceed.
Here your find also another comment from my why we didn't implement all the features/options of these video integrations in the core https://forge.typo3.org/issues/77710#note-4
I don't want to say we will not add extra options to the core regarding the video options. But just want to point out what the original idea behind it was. Don't give the editor to much to choose by default :)
Options that IMO make sense:
- start point (https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_HTML5_audio_and_video#Specifying_playback_range)
But only if these are available for all core video renderers or can be hidden for the files that don't provide these options.
#5 Updated by Guido S. about 2 years ago
Thanks for your detailed feedback. I understand your intention, but... ;-)
My 2 Cents:
- Extend TCA is for developers and not for interators (See TCCI/TCCD exam ;-))
- If you don't give the full rights for fields you can exclude the fields in be groups. Admins should see all possible fields.
I left over the decision for you. If you are happy with this standard, you can close this ticket :-)
(BTw: We extend per TCA, too)