Fix: Browser <title> tag is not rendered when overriding content_title in custom templates

[matixxd1999]

When creating a custom template that extends @EasyAdmin/page/content.html.twig and overriding the content_title block (as recommended by the deprecation notices), the browser's <title> tag remains empty.

[javiereguiluz]

Thanks for fixing this bug @matixxd1999.

[Seb33300]

This fix looks weird to me.

On the same template we have:

{% block page_title %}{{ block('content_title') }}{% endblock %}
{% block content_title %}{{ block('page_title') }}{% endblock %}

[matixxd1999]

Hey @Seb33300, I agree it looks like a circular dependency at first glance!

However, it's a necessary "Twig bridge" to maintain backward compatibility without breaking the layout. Because Twig evaluates the final overridden block from the child template first, it doesn't cause an infinite loop. It just links both blocks depending on what the user overrides:

• If you use the new way (content_title): page_title acts as a proxy and passes your text up to the browser's <title> tag in layout.html.twig.
• If you use the legacy way (page_title): content_title acts as a proxy and passes your text to the <h1> tag inside the content body.

Without this, the previously empty page_title block was just swallowing the value and leaving the browser tab completely blank when using content_title!