---
title: "Important: #111280 - Honeypot renders its fluidAdditionalAttributes"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:important-111280-1794315080"
source: "Changelog/14.3.x/Important-111280-HoneypotRendersFluidAdditionalAttributes.rst"
typo3-version: "14.3.x"
typo3-major: 14
type: "important"
issue: 111280
forge: "https://forge.typo3.org/issues/111280"
tags: ["Frontend", "YAML", "ext:form"]
rendered: "2026-11-19T09:58:06+00:00"
---

# Important: #111280 - Honeypot renders its fluidAdditionalAttributes {#important-111280-1794315080}

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

## Description {#description}

The form element `Honeypot` of EXT:form now renders the attributes
configured in `properties.fluidAdditionalAttributes`, as every other
form element does. Before, the frontend partial
`EXT:form/Resources/Private/Frontend/Partials/Honeypot.fluid.html`
ignored the property, so the values the form editor wrote into it never
reached the markup.

The `Honeypot` prototype now ships `autocomplete: 'off'` as
default in `properties.fluidAdditionalAttributes`. This keeps browser
form fillers from populating the honeypot, which made the submission of a
real person fail validation.

The attribute `aria-hidden="true"` is still rendered. With
`renderAsHiddenField: true` the honeypot is rendered as an input of
type "hidden" and carries none of these attributes.

## Impact {#impact}

The visible honeypot input carries `autocomplete="off"` and every
other attribute configured in its `properties.fluidAdditionalAttributes`.
Configuration that had no effect so far is now rendered.

Installations that override the partial `Honeypot.fluid.html` keep
their own markup and do not get the new attributes.
