Issue Feature Closed

#109734CKEditor5 link balloon shows raw t3://page?uid= instead of resolved page title

Thomas Esterer 04/30/26, 06:50 updated 10/15/26, 19:28

Description

When hovering over or clicking an internal page link in the CKEditor5 RTE, the link balloon popup displays the raw internal link format (e.g. “t3://page?uid=3249”) instead of the human-readable page title.

This is not meaningful for editors and makes it impossible to verify which page a link actually points to without opening the link browser.

**Steps to reproduce:**
1. Open a content element with a RTE field in the TYPO3 backend
2. Set an internal page link via the link browser
3. Save the content element
4. Re-open the content element for editing
5. Click on the internal link in CKEditor5 → The balloon shows “t3://page?uid=XXXX” instead of the page title

**Expected behavior:**
The link balloon should resolve the internal t3://page?uid= reference and display the human-readable page title, e.g. “Impressum” instead of “t3://page?uid=3249”.

**Actual behavior:**
The raw t3://page?uid=XXXX string is shown in the balloon.

**Background:**
The Typo3Link CKEditor5 plugin (typo3-link.js) renders the balloon using the raw href attribute value from the DOM without resolving it via the
TYPO3 backend API. A fix would require the plugin to perform an async lookup (e.g. via the existing backend link info endpoint) to resolve t3://page?uid=X to the corresponding page title before rendering the balloon.

Reviews 0

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

History 3

  1. Garvin Hicking commented and changed priority Should have Could have target version Complexity medium <span data-processor="relativetime" data-value="2026-04-30T07:00:34+00:00" > 04/30/26, 07:00 </span>

    Indeed this is not as straight ahead. An AJAX lookup also needs to evaluate page permissions and all (which the link browser does, but with a lot of logic).

    I do recognize this would be something nice to have, but I’m lowering the priority a bit, hope you can understand in terms of prioritization.

  2. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2026-10-15T19:28:04+00:00" > 10/15/26, 19:28 </span>

    closed with #99678 for v15, no backport will be done for v14