Issue Bug Closed

#111513Dark mode in CK Editor broken in 14.3.12 and 13.4.40

Sebastian Fischer 11/20/26, 07:39 updated 11/20/26, 16:01

Description

Since the update to 14.3.12 (and 13.4.40 in a different installation) the CK Editor shows white background when the dark mode is turned on. Before that version the editor had a dark background when in dark mode.

Before testing it was made sure that no custom css was loaded.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 2

History 4

  1. Sebastian Fischer commented <span data-processor="relativetime" data-value="2026-11-20T08:21:27+00:00" > 11/20/26, 08:21 </span>

    In 13.4.35 the background was defined with this

    :root {
    —token-color-neutral-0: #fff;
    —token-color-neutral-93: #121212;
    —typo3-surface-container-lowest: light-dark(var(—token-color-neutral-0), var(—token-color-neutral-93));
    —typo3-rte-base-bg: var(—typo3-surface-container-lowest);
    —ck-color-base-background: var(—typo3-rte-base-bg);
    }
    .ck.ck-editor__main>.ck-editor__editable {
    background: var(—ck-color-base-background);
    }

    Also the font has some problems too.

    Maybe we could apply this on top of the default css:
    .ck.ck-editor__main > .ck-editor__editable {
    —ck-editor-editable-background: var(—typo3-rte-base-bg);
    —ck-content-font-color: var(—typo3-rte-base-text);
    }

  2. Garvin Hicking commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-11-20T15:43:12+00:00" > 11/20/26, 15:43 </span>

    I just tried a vanilla MAIN and v14.3 installation. I cannot reproduce your issue I’m afraid. Dark mode shows up just fine for me in the camino site?! Please check if you have any custom RTE preset overloading custom CSS?

  3. Garvin Hicking commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-11-20T16:01:50+00:00" > 11/20/26, 16:01 </span>

    I’m closing the issue, it was caused by a custom YAML:

    editor:
      config:
        contentsCss: "EXT:ew_evoweb/Resources/Public/Css/rte.css"

    instead of:

    editor:
      config:
        contentsCss:
          - "EXT:ew_evoweb/Resources/Public/Css/rte.css"

    Only with the latter syntax it is ensured that TYPO3 overlays its own CSS for light/darkmode awareness. The former completely takes over styling (which is valid, too)