Feature #78264
open
Better support for html5 video/audio attributes
Added by Guido S. about 8 years ago.
Updated over 5 years ago.
Description
Hi,
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)
Additionally:
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.
Best regards
Files
Related issues
1 (1 open — 0 closed)
- Status changed from New to Needs Feedback
Hi,
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.
Hi Frans,
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 @Guido Schmechel)
Hi Guido,
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.
Groet Frans
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)
Best regards,
Guido
- Tracker changed from Bug to Feature
- Category set to Backend API
- Status changed from Needs Feedback to New
- Target version changed from 8 LTS to 9 LTS
Move this as feature to v9
- Status changed from New to Under Review
- Target version changed from 9 LTS to Candidate for Major Version
- Status changed from Under Review to New
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by