---
title: "Feature: #108148 - Alternative Fluid syntax for CDATA sections"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-108148-1763288461"
source: "Changelog/14.0/Feature-108148-AlternativeFluidSyntaxForCDATASections.rst"
typo3-version: "14.0"
typo3-major: 14
type: "feature"
issue: 108148
forge: "https://forge.typo3.org/issues/108148"
tags: ["Fluid", "ext:fluid"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Feature: #108148 - Alternative Fluid syntax for CDATA sections {#feature-108148-1763288461}

See [forge#108148](https://forge.typo3.org/issues/108148)

## Description {#description}

A long-standing issue in Fluid templates has been that the Fluid variable
and inline ViewHelper syntax collides with inlined CSS or JavaScript code.
This issue has now been addressed with Fluid 5: A new alternative syntax
has been introduced that makes collisions between CSS/JavaScript and Fluid
far less likely.

The normal inline and variable syntax uses single curly braces `{ }` as
tokens in Fluid templates. In `<![CDATA[ ]]>` sections, this syntax is now
ignored. Instead, three curly braces `{{{ }}}` can be used to call Fluid
ViewHelpers or to access variables. The tag-based syntax is disabled
altogether in CDATA sections.

Example:

```html
<f:variable name="color" value="red" />
<style>
<![CDATA[
    @media (min-width: 1000px) {
        p {
            background-color: {{{color}}};
        }
    }
]]>
</style>
```

The Fluid Explained documentation contains several practical examples of how
this new feature can be used:
[Avoiding syntax collision with JS and CSS](https://docs.typo3.org/other/typo3fluid/fluid/main/en-us/Syntax/Escaping.html#escaping-workarounds).

Note that it's still considered bad practice to put inline CSS or JavaScript
code in Fluid templates. Consider using a dedicated API endpoint, `data-*`
attributes or CSS custom properties (also known as CSS variables) to pass
dynamic values to JavaScript and CSS.

## Impact {#impact}

Inline CSS and JavaScript can now be wrapped in CDATA in Fluid templates,
which prevents syntax collision with Fluid's inline syntax.

CDATA sections are thus no longer removed from Fluid templates before
rendering, see
[Breaking: #108148 - CDATA Sections No Longer Removed](https://docs.typo3.org/permalink/changelog:breaking-108148-1763289953).