Skip to content

feat(reveal.js): Add support for tabset fragments in Reveal.js presentations - #13752

Closed
mcanouil wants to merge 7 commits into
quarto-dev:mainfrom
mcanouil:fix/issue13712
Closed

mcanouil wants to merge 7 commits into
quarto-dev:mainfrom
mcanouil:fix/issue13712

Conversation

@mcanouil

@mcanouil mcanouil commented Dec 3, 2025 •

Copy link
Copy Markdown
Collaborator

Introduce support for tabset fragments in Reveal.js presentations, enabling incremental content reveal within tabs during presentations.

Update the changelog to reflect this new feature.

Code originally from https://github.com/mcanouil/quarto-revealjs-tabset

Feature request: #13712

Example:

---
title: "Quarto Playground"
format: revealjs
---

## Slide

:::: {.panel-tabset}

### Tab 1

This is a playground for Quarto.

### Tab 2

{{< lipsum 1 >}}

### Tab 3

![An image]({{< placeholder 600 400 >}}){#fig-placeholder}

:::

@mcanouil mcanouil self-assigned this Dec 3, 2025
@posit-snyk-bot

posit-snyk-bot commented Dec 3, 2025 •

Copy link
Copy Markdown
Collaborator

✅ Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@mcanouil
mcanouil requested a review from cderv December 3, 2025 19:15
Added author information for the tabset fragments feature in Reveal.js presentations.
@mcanouil mcanouil changed the title feat: Add support for tabset fragments in Reveal.js presentations feat(reveal.js): Add support for tabset fragments in Reveal.js presentations Dec 6, 2025
@cscheid cscheid added this to the v1.10 milestone Feb 17, 2026
@mcanouil mcanouil modified the milestones: v1.10, v1.11 Jul 30, 2026
@mcanouil
mcanouil marked this pull request as draft October 19, 2026 11:53
@cderv cderv modified the milestones: v1.11, v1.12 Oct 29, 2026
@mcanouil

Copy link
Copy Markdown
Collaborator Author

Closing in favour of #15332, which rebuilds this as an opt-in tabset-fragments option.
It keeps one fragment order per slide, so incremental: true and stepped code highlights no longer collide with the tabs, and it shows the right tab after going back or following a deep link.

@mcanouil mcanouil closed this Nov 10, 2026
@mcanouil
mcanouil deleted the fix/issue13712 branch November 10, 2026 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants