#107093Incomplete Dropdown Display in Inline Element
Description
When editing a custom content element in TYPO3, the dropdown menu inside the inline element—specifically the “Style” dropdown in the t3editor—is not fully visible. The style options are cut off and extend outside the visible container.
Steps to Reproduce:
- Go to any page in the TYPO3 backend.
- Create or edit a content element of type Step Points.
- Within the inline record, go to the “Text” field using the RTE (t3editor).
- Click on the “Style” dropdown.
Reviews 2
Related issues 1
Files 2
History 12
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2025-07-14T14:55:19+00:00" > 07/14/25, 14:55 </span>
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2025-07-14T15:03:14+00:00" > 07/14/25, 15:03 </span> -
Tiran Grigoryan commented <span data-processor="relativetime" data-value="2025-07-14T15:42:27+00:00" > 07/14/25, 15:42 </span>
Hello @ghi,
I have Typo3 version 13.4.15. I also set height to 300, but it had no effect. Please take a look at the video. https://www.loom.com/share/fed2c19cc1c646049b367f70bde3fde3
Here is the RTE configuration.
$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['default'] = 'EXT:system/Configuration/RTE/default.yaml';imports: - { resource: "EXT:rte_ckeditor/Configuration/RTE/Processing.yaml" } - { resource: 'EXT:rte_ckeditor/Configuration/RTE/Editor/Plugins.yaml' } - { resource: "EXT:system/Configuration/RTE/StylesSets/headlines.yml" } - { resource: "EXT:system/Configuration/RTE/StylesSets/text.yml" } - { resource: "EXT:system/Configuration/RTE/StylesSets/list.yml" } allowedOptions: 'target,title,class,params,rel' allowedTypes: 'page,url,telephone,email' editor: config: height: 300 language: 'de' allowedContent: true contentsCss: - 'EXT:system/Resources/Public/assets/css/main.css' format_tags: "p;h1;h2;h3;h4;h5;h6,span" allowTags: - span toolbar: - [ 'Style', 'Heading' ] - [ 'Bold'] - [ 'BulletedList', 'Alignment'] - [ 'Link', 'Unlink' ] - [ 'Undo', 'Redo' ] - [ 'Source' ] alignment: options: - { name: 'left', className: 'text-start' } - { name: 'center', className: 'text-center' } - { name: 'right', className: 'text-end' } - { name: 'center-md', className: 'text-md-center' } - { name: 'right-md', className: 'text-md-end' } extraPlugins: - justify removeButtons: - Underline - Strike - SpecialChar - Table - Cut - Copy - PasteFromWord - Subscript - Superscript - JustifyBlock - Blockquote importModules: - { module: '@ckeditor/ckeditor5-word-count', exports: [ 'WordCount' ] } -
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-07-14T15:47:48+00:00" > 07/14/25, 15:47 </span>
Does this also happen if you remove your preset and use the internal one? And how does your “EXT:system/Resources/Public/assets/css/main.css” file look like?
-
Tiran Grigoryan commented <span data-processor="relativetime" data-value="2025-07-14T16:20:02+00:00" > 07/14/25, 16:20 </span>
@ghi The file `EXT:system/Resources/Public/assets/css/main.css` does not exist, so I have commented it out.
As for the my preset configuration, there are only a few options:
packages/system/Configuration/RTE/StylesSets/text.yml: editor: config: stylesSet: - { name: "p class display-1", element: "p", attributes: { class: "display-1" } } - { name: "p class display-2", element: "p", attributes: { class: "display-2" } } - { name: "p class display-3", element: "p", attributes: { class: "display-3" } } - { name: "p class display-4", element: "p", attributes: { class: "display-4" } } - { name: "p class display-5", element: "p", attributes: { class: "display-5" } } - { name: "p class display-6", element: "p", attributes: { class: "display-6" } } - { name: "p class fs-1", element: "p", attributes: { class: "fs-1" } } - { name: "p class fs-2", element: "p", attributes: { class: "fs-2" } } - { name: "p class fs-3", element: "p", attributes: { class: "fs-3" } } - { name: "p class fs-4", element: "p", attributes: { class: "fs-4" } } - { name: "p class fs-5", element: "p", attributes: { class: "fs-5" } } - { name: "p class fs-6", element: "p", attributes: { class: "fs-6" } } - { name: "Rot", element: "span", attributes: { class: "text-red"} } - { name: "Leicht Rot", element: "span", attributes: { class: "text-red-light"} } - { name: "Grün", element: "span", attributes: { class: "text-green"} }Even when I use the default RTE settings, I can still reproduce the issue once I add my own presets, because they include many default styles — and that causes the dropdown to require scrolling.
vendor/typo3/cms-rte-ckeditor/Configuration/RTE/Default.yaml style: definitions: - { name: "Lead", element: "p", classes: ['lead'] } - { name: "Small", element: "small" } - { name: "Muted", element: "span", classes: ['text-muted'] } -
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-07-14T18:05:06+00:00" > 07/14/25, 18:05 </span>
Ah! Now I can see it. Yes, in my tests I did not have enough options and did not check with an IRRE child that had an RTE as the last item.
I can reproduce your bug now. I’ll commit a patch to showcase the behaviour and then I’ll try to involve someone who knows their way with CSS better than I do ;-)
-
Garvin Hicking changed Related to #107096 <span data-processor="relativetime" data-value="2025-07-14T18:09:48+00:00" > 07/14/25, 18:09 </span>
-
Tiran Grigoryan commented <span data-processor="relativetime" data-value="2025-07-15T05:54:21+00:00" > 07/15/25, 05:54 </span>
Garvin Hicking wrote in #note-6:
> Ah! Now I can see it. Yes, in my tests I did not have enough options and did not check with an IRRE child that had an RTE as the last item.
>
> I can reproduce your bug now. I’ll commit a patch to showcase the behaviour and then I’ll try to involve someone who knows their way with CSS better than I do ;-)Thank you very much. :)
-
wini2 no-lastname-given commented <span data-processor="relativetime" data-value="2025-07-23T15:51:25+00:00" > 07/23/25, 15:51 </span>
Hello,
maybe it does not exactly meet the problem, but I had to struggle with similar issues. The dropdown ist much to small for speaking description. In seach of a solution I first blamed it on ckeditor (to add to the list of shortcomings of this poor editor). After hours of searching on ckeditor-solution, I noticed, that the problem lies with the css which comes with TYPO3. After toying around with the backend.css the solution for me was something like.ck.ck-dropdown .ck-dropdown__panel.ck-dropdown__panel_se {
min-height: 500px;
/*min-height: fit-content;/*
}.ck.ck-style-panel {
resize: both;
/* scrollbar-gutter: stable; */
min-width: 608px;
max-width: 650px;
}.ck.ck-style-panel .ck-style-grid .ck-style-grid__button {
padding: 0;
width: 180px !important;
}It would have been helpfull if the documentation hints to something like that.
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-07-23T16:41:02+00:00" > 07/23/25, 16:41 </span>
This is definitely a bug/problem with our CSS, and something we should try to fix. I’m not sure the hotfix pasted worka in all devices and resolutions thougb, but I’m happy to hear that this helps in your case!
-
Riccardo De Contardi commented <span data-processor="relativetime" data-value="2025-11-05T10:05:15+00:00" > 11/05/25, 10:05 </span>
IMHO the problem here lies in the fixed
max-heightof.ck.ck-style-panel(--ck-style-panel-max-height: 470px)The ideal would be to calculate the available height dynamically, I guess
-
Georg Ringer commented and changed attached Bildschirmfoto 2026-10-06 um 09.47.44.png status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-10-06T07:48:24+00:00" > 10/06/26, 07:48 </span>Bildschirmfoto%202026-10-06%20um%2009.47.44.png
cant be reproduced in 14
Hi,
can you tell which exact TYPO3 v13 patchlevel version you’re using? What’s odd is that your design has some differences: The height of the input area is less than TYPO3 emits (min-height: 300px) and the “powered by ckeditor” footer below looks different in recent versions (no longer in ‘the footer’ but embedded inside the main editable area).
I’m asking because I believe this is no longer a problem in current CKEDitor versions bundled with recent TYPO3.
Otherwise, a custom
content.cssfile might be the cause of this?