Passing HTML into nested fragments doesn't work

[oniekrenz]

I wanted to use the following structure but it doesn't work.

test.html

<th:block layout:fragment="a">
    <div layout:include="test::b">
        <div layout:fragment="b-content">
            <th:block layout:fragment="a-content"/><!-- doesn't work -->
        </div>
    </div>
    <th:block layout:fragment="a-content"/><!-- works -->
</th:block>

<th:block layout:fragment="b">
    <th:block layout:fragment="b-content"/>
</th:block>

template.html

<div layout:include="test::a">
    <th:block layout:fragment="a-content">A content</th:block>
</div>

It seems to me that the nested fragment reference 'a-content' can't be interpreted as such. Instead it it interpreted as setting a 'a-content' fragment parameter for fragment b. This is caused by the ambiguity of the 'layout:fragment' attribute which serves for both purposes.
Instead another 'layout:fragmentref' attribute could help but this would ruin all existing scripts.

[oniekrenz]

I think I found a solution.
AbstractContentProcessor.findFragments:85 proceeds to recurse even if a fragmentname has been found, which IMHO does not make sense. Recursing should only be done when fragmentname is null which can be achieved by adding an else branch to the first if statement:

} else if (!hasAttribute(element, DIALECT_PREFIX_LAYOUT, PROCESSOR_NAME_INCLUDE) &&

[ultraq]

Closing - conversation continued in linked PR.