Review main Abandoned

91078[POC][TASK] Add htmx instead of iframe

Benni Mack CR 0 V 0 Hard +335 −12 updated 04/21/26, 15:09

Commit message

This change adds htmx which allows us to load
content of mdoules directly instead of iframes.

The most important part here is that it is opt-in,
thus, it could be used for certain modules to ship
HTML via fluid, while removing the iframe.

This is a quick PoC to see if we can actually work
like this.

Review

  • Code review CR 0
  • Verified V 0
    • core-ci +1 CI

Files 20

Review log 57

  1. Benni Mack uploaded patch set 1 10/15/25, 11:37

  2. core-ci voted on patch set 1 V -1 10/15/25, 11:46 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86715

  3. Benjamin Franzke uploaded patch set 2 V -1 10/16/25, 04:06

  4. core-ci voted on patch set 2 V +1 10/16/25, 04:13 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86775

  5. Benjamin Franzke commented on patch set 2 10/16/25, 04:13

    htmx.ts:47 Unresolved

    I would not allow script tags and instead send a specific header that returns a structured information about the JavaScript modules to be loaded. That combined with the following patch to allow all JavaScript imports on the top frame (without explicit tagging) > 90103: [TASK] Include all importmap configuration in authorized contexts | https://review.typo3.org/c/Packages/TYPO3.CMS/+/90103 could allow to load JavaScript modules without degrading security. Also the module request in htmx mode could then be in a somewhat "strict" mode to only allow side-effect free JavaScriptModuleInstructions (e.g. those without initialization callbacks). but all of that requires that the uses JavaScript modules are robust and prepared for runtime DOM modification (e.g. needs to use delegators instead of plain element event listeners in order to pick up events)
  6. Benni Mack marked it work in progress 10/16/25, 19:32

  7. Benni Mack abandoned the change 04/21/26, 15:09

    won't do