Repository navigation
Conversation
mcanouil
added
enhancement
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
mcanouil
force-pushed
the
feat/revealjs-tabset-fragments-13712
branch
from
November 10, 2026 16:58
61201d3 to
853f463
Compare
This was referenced Nov 10, 2026
Step through the tabs of a tabset as fragments when `tabset-fragments` is on, or when a tabset has the `.tabset-fragments` class. The `.no-tabset-fragments` class opts one tabset out. The plugin gives the slide one fragment order, so incremental lists, stepped code highlights and explicit fragment indices do not collide with the tabs. The shown tab follows the fragment state after going back, a deep link, a click or in scroll view, and tab switches go through tabby. In PDF, each step gets a page, or each tab state gets one with `pdf-separate-fragments: false`.
mcanouil
force-pushed
the
feat/revealjs-tabset-fragments-13712
branch
from
November 10, 2026 17:24
853f463 to
0093db5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This adds a
tabset-fragmentsoption for Reveal.js decks.When it's on, each tabset steps through its tabs as fragments, and the fragments inside a tab show before the next tab.
The
.tabset-fragmentsand.no-tabset-fragmentsclasses turn it on or off for one tabset.The option is off by default, and a deck that doesn't use it renders exactly as before, as the plugin isn't loaded.
The plugin gives the whole slide one fragment order, so
incremental: true, stepped code highlights and explicitfragment-indexvalues don't collide with the tabs.The tab shown always follows the fragment state, including after going back, a deep link, or a click on a tab.
Tab switching goes through tabby, so the keyboard order from #15155 and #15007 still works.
In PDF,
pdf-separate-fragments: truegives a page per step.With
false, each tab gets its own page, numberedN.1,N.2and so on.This replaces #13752, and comes from my extension
mcanouil/quarto-revealjs-tabset, which will defer to this option.It answers discussion #13712.
The docs pull request is quarto-dev/quarto-web#2353.
The screencast steps through one slide: a fragment in the first tab, a stepped code highlight in the second, and a fragment in the third.
tabset-fragments.mp4
Checklist
I have (if applicable):
AI-assisted PR
Note: autonomous AI agents submitting PRs without human oversight are not permitted — see the Code of Conduct.