Martin Auswöger

This PR should finished now I think. I updated the notes section in https://github.com/contao/contao/pull/6859#issue-2119617501 Once doctrine/dbal 4.3.0 gets released we are ready 🎉

I just noticed that merging this would implicitly increase our minimum supported versions to MySQL 5.7.9 and MariaDB 10.4.3. Are we fine with that?

> but we should not do it in Contao 5.3 @fritzmg can you change the base branch to 5.x?

`doctrine/dbal` version `4.3.0` was just released: https://github.com/doctrine/dbal/releases/tag/4.3.0 Would be great if we could get this into the 5.6 release.

> We shouldn't remove something that _could_ provide value It harms the usabililty for people that have a screenreader with title attributes enabled, see https://github.com/contao/contao/issues/6361#issuecomment-1702495691 > especially if it means...

The `true` to get the value without any encoding. In this case you need to make sure it gets properly encoded in all places where it is output to the...

You can find more details of how the `Input` encoding works here: https://github.com/contao/contao/pull/4453#issuecomment-1094112590

> Should we enable that by default for `tl_form_field.customRgxp`? I’m not sure. We never output it as HTML, right? (like as `` or so?)

Do these projects have more JSON files in *var/deferred-images* than they have images in *assets/images*? > Now, in both cases we solved this via a cronjob that simply deletes any...

> Do you mean more JSON files in `assets/images/deferred` than in `assets/images/…`? Yes, since Contao 5.0 they are stored in `var/deferred-images`. > We used to have that, but that got...