#96162Extend Video via Text&Media to accept Player Options for Youtube
Description
Youtube allows URL parameters to customize the embedded Player, see https://developers.google.com/youtube/player_parameters#Parameters
From TYPO3 Text&Media CE, only autoplay is supported.
In contrast, the file typo3/sysext/core/Classes/Resource/Rendering/YouTubeRenderer.php in method createYoutubeUrl would be able to cater for the parameters.
Sys_file_reference should be extended to accept Player Parameters to be set by editors.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[TASK] Extend Video via Text&Media to accept Player Options for Youtube Resolves: #96162 Releases: main
History 1
-
Georg Ringer commented and changed TYPO3 Version
1214 <span data-processor="relativetime" data-value="2026-10-17T09:45:56+00:00" > 10/17/26, 09:45 </span>
The request is valid: only a small part of the YouTube player parameters can be influenced today.
What is possible now:
YouTubeRendererevaluates the optionscontrols,autoplay(enforcesmute=1),modestbranding,loop,relatedVideos,enablejsapiandno-cookie.autoplayis additionally read from the file reference itself.<f:media>passesadditionalConfigto the renderer. EXT:fluid_styled_content hands oversettings.media.additionalConfiginPartials/Media/Rendering/Video.fluid.html, so these options can be set globally in TypoScript, or per element in an own template.sys_file_reference(or the content element) and pass its value asadditionalConfig.What is not possible without an own renderer:
start,end,cc_load_policy,cc_lang_pref,color,disablekb,fs,hl,iv_load_policy,list,listType,playsinlineandwidget_referrer.autohide=1is hardcoded.Possible directions
additionalConfig.additionalConfig['urlParameters']array that is appended to the embed URL. Integrators could then setstart,endand others without an own renderer or a new database field. Points to consider: the parameters set by the renderer itself (autoplay/@mute@,enablejsapi,origin) must stay protected, values need to be encoded, and the Vimeo renderer has the same need.sys_file_referencefor selected parameters (for examplestartandend). This puts provider specific fields into every installation.Feedback on which direction makes sense is welcome.