Skip to content

fix(preview): give each document its own heading fold state #425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PathGao merged 1 commit into from
Aug 3, 2026
Merged

fix(preview): give each document its own heading fold state #425

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion scripts/editorPdfExport.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -368,7 +368,12 @@ test('the refresh is skipped when the DOM already matches the buffer', () => {

test('the refresh actually lands before the print', () => {
const body_ = slice(viewer, 'async function syncPreviewForPrint', 'async function exportAsPdf');
assert.match(body_, /await renderMarkdownPreview\(rawContent, tab\.path\)/);
// What matters here is WHAT is rendered — this tab's buffer and this tab's
// path, not the disk — and that it is awaited before the content is
// swapped in. The trailing arguments are deliberately not pinned: fold
// state is one of them and it is the renderer's business, not the
// export's.
assert.match(body_, /await renderMarkdownPreview\(rawContent, tab\.path[,)]/);
assert.match(body_, /tabManager\.updateTabContent\(tabId, processed\)/);
// Mermaid, KaTeX and highlight.js all replace nodes asynchronously. The
// on-screen path fires and forgets; the export cannot.
Expand Down
Loading
Loading