Project

General

Profile

Actions

Bug #104490

open

Undocumented effects of avoiding registerTagAttribute() in VH's

Added by Eric Harrer about 14 hours ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Fluid
Target version:
Start date:
2024-07-26
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

With commit https://github.com/TYPO3/typo3/commit/21d3f18b0ee8c7e2915f2ca3d054704ce06a4ec4 occurrences of registerTagAttribute() in VHs were removed.

The HTML output behaviour of Boolean attributes, which were previously defined via registerTagAttribute() , has changed in the event that the attribute was set without a value .

It can happen that inline conditions are used in extensions in the context of the fluid attribute, which should be decisive for whether the boolean attribute should be output in HTML or not.

Example

<f:form.textarea name="myname" value="myvalue" readonly="{f:if(condition:anyCondition,then:'1')}" />

If in the example anyCondition is FALSE , then the attribute readonly is not used in HTML in TYPO3 v12 and is now used in TYPO3 v13. This is therefore a breaking change that should be documented so that extension maintainers can react appropriately to the new feature.

EXT:translate_locallang can also be analysed to evaluate the possible effects.
Issue: https://github.com/rrrapha/translate_locallang/issues/81
Fix: https://github.com/rrrapha/translate_locallang/pull/82


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #104443: Avoid registerTagAttribute() in VH'sResolved2024-07-20

Actions
Actions #1

Updated by Eric Harrer about 14 hours ago

  • Related to Task #104443: Avoid registerTagAttribute() in VH's added
Actions

Also available in: Atom PDF