Review main Ready for review Quiet Breaking

93332[!!!][BUGFIX] Move bodytext into its own palette

Christian Jung CR -2 V -1 Normal +227 −3 updated 10/23/26, 21:26

Commit message

The bodytext field of the content elements "text", "textmedia" and
"textpic" moves into a palette labeled "Text Content". That gives
screen readers a heading for the field.

Each content type gets its own palette. A positioned change such as
replace:bodytext for one type therefore does not rewrite the palette
of the others. before:bodytext and after:bodytext still change only
the listed types, and they place new fields next to the palette
rather than inside it.

Test this change

Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch

Check out patch set 4
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/32/93332/4 && git checkout FETCH_HEAD
Cherry-pick onto main
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/32/93332/4 && git cherry-pick FETCH_HEAD

Review

  • Code review CR -2 Blocked
    • Benni Mack -2
    • Christian Rath-Ulrich +1
  • Verified V -1 Blocked
    • Christian Rath-Ulrich +1
    • core-ci -1 CI

Merge conflicts 7

Issues 1

Files 7

Review log 913

  1. Christian Jung uploaded patch set 1 03/24/26, 14:43

  2. core-ci voted on patch set 1 V +1 03/24/26, 14:53 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98603

  3. Georg Ringer voted on patch set 1 CR +1 V +1 03/24/26, 16:38

  4. Garvin Hicking commented on patch set 1 CR -1 03/25/26, 08:06

    I understand the intention behind this, but changing it like this will affect code paths like: ``` ExtensionManagementUtility::addToAllTCATypes('myfield', 'tt_content', 'after:bodytext', 'myCType'); ``` which will then add fields in the palette and then affect every place than just `myCType`. There might be other side effects that this will have to ordering assignments. Since we are very close to the LTS release this is a change that could create friction and side-effects that are better placed in a `.0` release. And we would also need at least an "important.rst" file describing possible edge cases. As such I would vote to delay this for v15. The change itself is good and appreciated for accessibility reasons, thanks a lot for contributing!
  5. Christian Rath-Ulrich uploaded patch set 2 CR +1 V +1 10/22/26, 15:26

  6. Christian Rath-Ulrich commented on patch set 2 10/22/26, 15:28

    Reply

    Done
  7. Christian Rath-Ulrich uploaded patch set 3 10/22/26, 15:28

  8. core-ci voted on patch set 2 V -1 10/22/26, 15:37 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/112130

  9. core-ci voted on patch set 3 V -1 10/22/26, 15:37 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/112131

  10. Garvin Hicking updated the commit message in patch set 4 V -1 10/22/26, 17:22

  11. core-ci voted on patch set 4 V -1 10/22/26, 17:31 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/112159

  12. Christian Rath-Ulrich voted on patch set 4 CR +1 V +1 10/23/26, 20:08

  13. Benni Mack commented on patch set 4 CR -2 10/23/26, 21:26

    I have to pause this unfortunately, as we probably need this in a bigger context change (extracting fluid styled content)