Conflict with markdown-it-container

When using this plugin with markdown-it container all the attrs for the elements inside get’s merged with the attrs for the container unless there are more than one level of nested containers.

If I set attrs for a container, it get’s inserted on the container attrs array as expected. (needs custom render function but that’s a bug for the container plugin)

Example input:

::: column {.is-8}
Lorem ipsum
:::

Current output:

<div class="column is-8">
<p>Lorem ipsum</p>
</div>

But if I set attrs on the child, the attrs are set on the container:

::: column {.is-8}
# Some title here {.title}

Lorem ipsum
:::

It outputs:

<div class="column is-8 title">
<h1>Some title here</h1>
<p>Lorem ipsum</p>
</div>

Expected output:

<div class="column is-8">
<h1 class="title">Some title here</h1>
<p>Lorem ipsum</p>
</div>

When using nested containers it works as expected

:::: columns {.is-mobile}
::: column {.is-8}

# lorem ipsum {.title}

more lorem ipsum

:::
::::

outputs:

<div class="is-mobile columns">
<div class="is-8 column">
<h1 id="lorem-ipsum" class="title">lorem ipsum</h1>
<p>more lorem ipsum</p>
</div>
</div>

[cesasol]

Attributes first, but I tested inverting the order and the result is the same.

[StefanZander]

I am using both extensions markdown-it-attrs and markdown-it-container in conjunction with Marp in order to create my lecture slides.

When combining both extensions, e.g.,

::: definition
some def text...

Source: some source text {.source}
:::

the .source class will be propagated to the definition container (the parent div) rather than to the paragraph that represents the source text.

The problem as described in post #1 is still present to me.

I also tried the workaround proposed by @mb21 but it does not work in my setup.

Since I really like both extensions, I hope there is another way of making both work together.

Thanks in advance.