[d-morrison]

Requested by Ezra · project thread

Quarto hoists a cross-referenced figure's details.code-fold blocks above the figure, so the R and Python folds stacked outside the tabset (example: https://morrison-lab.github.io/mds/optimization-convexity.html#fig-convex-set).

This adds tabset-code-in-tabs.html, an after-body script that moves each fold into the tab for its language, matching by language and falling back to order. It skips a tabset unless the folds before it equal its tab count. .gitignore gets an exception for the new file. The fold labels here already say "Show code".

Checked with jsdom on the published mds page; the PR preview should confirm it in a real render.

---

Generated by Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

[github-actions]

Claude finished review — View run

---

Commit a6262ed (reviewed as the range 3953bc7..a6262ed) adds one suggestion about the new slide selectors. I read the diff and made no render; Quarto isn't installed in this run. The earlier verdict on 3953bc79 is here: Ready for merge, no blocking findings.

Findings

tabset-code-in-tabs.html:11, suggestion (not blocking, unverified). The commit's goal is to make the fold move work on slides too. The new pane selector is :scope > .tab-content > div. As I recall, Quarto's reveal.js (tabby) tabsets put the pane divs directly under div.panel-tabset, beside the ul, with no .tab-content wrapper. If so, panes is empty on slides. The script then returns at the folds.length !== panes.length check and does nothing, with no error, so slides would keep the stacked folds. The website path is unaffected.

I couldn't confirm either way without a render. Before relying on the claim in the comment on line 7, render one slide deck and inspect the tabset DOM. If the panes are direct children, use a selector that matches both layouts. For example, take :scope > .tab-content > div when that wrapper exists, and otherwise :scope > div.

tabset-code-in-tabs.html:34-38, minor. unused() returns -1 when every tab is already used. The length checks above make that unreachable today. A later edit that relaxes them would make panes[-1].insertBefore throw. A one-line guard would avoid that. The new unused() fix does correct the earlier index-collision issue.

Checked

• _quarto-website.yml:206 adds include-after-body under the revealjs format, and the file path matches.
• No page paths, anchors, math or prose changed.

Verdict

Ready for merge. Nothing here blocks the merge. The line 11 selector is worth a render check, though.

Structured Review Data (JSON)

{
  "schema_version": "1.1",
  "reviewer": "claude",
  "commit_sha": "a6262ed4a7a5d2028be598d222f2a4bb9ff6a287",
  "verdict": "CLEAN",
  "findings": [],
  "detailed_assessment": "In tabset-code-in-tabs.html the slide pane selector may not match tabby's DOM, which would make the script a silent no-op on slides; unverified, and the unused() helper can return -1 only if the length guards are relaxed.",
  "holistic_assessment": "The change is small and scoped, the include-after-body wiring for revealjs is correct, and no page paths or anchors change; validation was by reading only because Quarto was unavailable to render."
}

Reviewed commit: a6262ed

[github-actions]

💰 Cost: $0.2101 (review) — run

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.

_{2026-10-31 00:28 UTC}