Section Numbers in Tabs and Table of Contents

[mojave-meow]

Hello. I was wondering if there is a way to include section numbers in the panel-tabset header names. When knitting an R Markdown file, the tabs were automatically labeled with the section number, e.g., "1.1.2 Tab B." However, Quarto does not add these section numbers automatically.

Additionally, when headers get put into tabs, they no longer appear in the table of contents. Is there a way to keep these headers in the table of contents? Thank you!

Example below. When rendered, ### Lower Header becomes "2.1.1. Lower Header," and it appears in the table of contents. However, the three tabs are not numbered and do not appear in the table of contents. Thank you!

---
title: "ToC and Tab Section Numbers"
format:
  html:
    toc: true
    toc-location: left
    toc-expand: 2
    toc-depth: 3
    toc-title: Contents
    number-sections: true
    number-depth: 3
---

# Section

## Subsection

::: panel-tabset

### Tab A

### Tab B

### Tab C

:::

# Section

## Subsection

### Lower Header

[cderv]

I believe in Quarto, this is by design the heading in tabset are only use as a mean to simply configure the tabset panel title. They are not processed as header by Pandoc, so no numbering are applied to them.

In R Markdown the tabset part was done in JS after pandoc processing, and so numbering was indeed shown.

For the TOC this is the same, tabset panel title are not considered headers to be put in TOC when the TOC is processed.

This would be feature request to advocate for a change of this behavior IMO

[mcanouil]

For what is worth, I don't think tabset should be numbered or part of a table of contents (it what I disliked the most in RMarkdown).

[cscheid]

Additionally, when headers get put into tabs, they no longer appear in the table of contents. Is there a way to keep these headers in the table of contents? Thank you!

Not currently, but I'll take into account for the crossref redesign I'm currently doing. This will never happen by default, since those headers are meant to indicate the titles of the tabs, and are not actually section headers (the same thing happens for callouts). But it might be possible to "force" the header behavior. No promises, but I'll keep it in mind.

[melaniewalsh]

I wanted to follow up on this question. Is there a way to include headers within tabs in the ToC in the latest version of quarto? @mojave-meow did you ever figure this out?

Thank you!

[cscheid]

Is there a way to include headers within tabs in the ToC in the latest version of quarto?

No, there isn't.

[m-clark]

This seems related: it appears that while tabs are unnumbered in the html, they are numbered in the pdf, and if they are at a proper depth, they'd be included in the ToC. I'd actually prefer they not be numbered or included in the ToC regardless of ToC depth, which seems would be consistent with the html. I tried one or two ways to remove the pdf numbering without success. Are there any suggestions for this? I can create a header depth to get them out of the ToC, but it results in a odd numbering to do so.

Test the above demo doc by adding the following as one example:

  pdf:
    toc: true
    toc-title: 'Contents'
    number-sections: true

[mariashinoto]

Quarto 1.3.450 here. I render PDF and HTML (Book) from a Quarto document, and the headers for the tabs in the tab panes

• appear unnumbered in the outline (TOC) of visual editing modes etc. in Visual Studio Code and RStudio
• appear unnumbered as tabs in the HTML render/preview as an HTML book without appearing in the TOC on the navbar (-> That is the expected behavior)
• appear numbered and as titles in the PDF (text and TOC).
  • They are even numbered although I added `{.unnumbered}' to prevent the worst: different chapter numbers in HTML and PDF. (-> unexpected behavior)
  • They are in my case numbered as h4, although I added five hashes #####. But the toc-depth in Quarto YAML is set to 4. (-> unexpected behavior)

So I suspect that HTML works correctly, while the other outputs do need some polishing. Or is there a solution in the meantime that I have overlooked?

[mcanouil]

No changes in that matter is to be expected in 1.3.
The "crossref redesign" is in 1.4.

[mariashinoto]

Thanks, hoping for version 1.4 and updating...