Simon Praetorius
Simon Praetorius
@sascha-egerer In general, I like the added type definitions there. However, I'm not sure about the arbitrary arguments to `` mixing with `name` (and possible future built-in arguments?).
Related: #1044
Ah sorry, I was a bit unclear: The feature would only be to add the two TypoScript properties and to hand them to the `` in the template. The code...
> > I think we should have a close look at syntax and restrictions. We may also want to see if such a system could be an opportunity to have...
So to sum up, you would like to change the behavior for `NULL` values, everything else is fine? I think we previously chose to leave the `NULL` behavior as-is to...
I'm still confused about the fixation to switch from `disabled="disabled"` to just `disabled`, I've heard this one several times. Isn't it just the same result, only a different syntax?
Yeah, but... why change it? I don't get it. Isn't it just a matter of taste?
Yes, that's why I asked if it's mainly about `null`. Let's not mix code style choices with actual issues that have consequences in functionality.
In a first step, yes. The `null` change would be breaking and needs to be evaluated, e. g. against the TYPO3 Core. This is a runtime change for ViewHelpers, which...
From what I understand, this is the actual issue: ```xml ``` will lead to: ```xml ``` instead of removing that attribute altogether. This comment shows that we already thought about...