Is flat (single-level) nesting of DIV spans supported?

[wlatendresse]

Description

Let’s consider the following example, which essentially contains several blocks intended for different groups of recipients, all of which are enclosed within a block that is definitely not supposed to be included in the final version.:

---
title: Nested blocks
authors:
  - name: Norah Jones
---

::: {.content-visible unless-profile="final"}

::: {.callout-todo}
```
TODO: TODO 1
TODO: TODO 2
TODO: TODO 3
TODO: TODO 4
```
:::

::: {.callout-note}
**Instructions for my subordinates regarding “foo bar”:**

Do some "foo bar" and then check the results.
:::

::: {.callout-note}
**Instructions for my helpers who live far away regarding “foo baz”:**

- Do some foo.
- Do some baz.
- Check the results.
:::

:::

Is and should this kind of structure (div span including several blocks, or to put it another way: the last block delimiter belongs to the first block delimiter shown in the example) be supported, or is nesting generally problematic?

[mcanouil]

Unclear, what you are asking here.

If you want three callouts (or whatever blocks) to be conditioned on "final" profile this is the DRY syntax.

In most cases you will even want to nest as .content-visible unless-profile="final" is removed with the div.

[wlatendresse]

@mcanouil
The markup shown above contains three different blocks, each targeting a different audience, enclosed within a block that acts as a safeguard to ensure that none of the three blocks are included when rendering via the “final” profile.

Of course, one could repeat “{.content-visible unless-profile=‘final’}” for each individual block, but we’re all programmers here, after all. That can’t be the solution.

So if your point is that this should work without any problems, then that would be perfectly sufficient for me.

[mcanouil]

So if your point is that this should work without any problems, then that would be perfectly sufficient for me.

It should. I'm using this all the time when writing multi-formats/audiences documents.

Side note: there is no need to ping on a thread with only two.

[mcanouil]

You can see a real life example of conditional content in https://github.com/mcanouil/mastering-quarto-cli

[wlatendresse]

Side note: there is no need to ping on a thread with only two.

Ping? The thumbs-up? Just take it as a thank-you for the quick reply—no strings attached.

[mcanouil]

When you mention someone, it triggers a louder notification.

[wlatendresse]

I wasn't aware of that.

Well, the actual problem doesn't seem to be the nesting of the blocks after all, but rather lies elsewhere, maybe in relation to Python execution.

See Issue 14479