Issue Task New Quiet

#96162Extend Video via Text&Media to accept Player Options for Youtube

Anja Leichsenring 11/30/21, 13:11 updated 10/17/26, 09:45

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

  1. Georg Ringer commented and changed TYPO3 Version 12 14 <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:

    • YouTubeRenderer evaluates the options controls, autoplay (enforces mute=1), modestbranding, loop, relatedVideos, enablejsapi and no-cookie. autoplay is additionally read from the file reference itself.
    • <f:media> passes additionalConfig to the renderer. EXT:fluid_styled_content hands over settings.media.additionalConfig in Partials/Media/Rendering/Video.fluid.html, so these options can be set globally in TypoScript, or per element in an own template.
    • An integrator who needs a per-element choice can add a field to sys_file_reference (or the content element) and pass its value as additionalConfig.

    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, playsinline and widget_referrer. autohide=1 is hardcoded.

    Possible directions

    1. Leave it as it is: editor-facing fields are a decision of the project (a tailored content element), the core offers the supported options through additionalConfig.
    2. Allow a generic additionalConfig['urlParameters'] array that is appended to the embed URL. Integrators could then set start, end and 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.
    3. New fields in sys_file_reference for selected parameters (for example start and end). This puts provider specific fields into every installation.

    Feedback on which direction makes sense is welcome.