quarto-dev / quarto-dev/quarto

Quarto outline not visible until after source/visual editor toggle or file edit

Open
#791 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug vscode
Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

Bug description

The quarto outline layout is not visible until a change to the file is triggered. Then the quarto outline shows up. E.g. I toggle the source view to visual view and the outline shows up again.

Steps to reproduce

Launch any quarto document with headings and without any changes, outline items may be blank and not picked up. If you switch from source to visual or according to @juliasilge, make any change to the file, the outline is populated again

Actual behavior

Outline items do not show up immediately upon launch, only repopulate upon edit to the document

Expected behavior

Outline items show up upon launch

Your environment

Positron Version: 2025.08.0 (system setup) build 130
Code - OSS Version: 1.102.0
Commit: 76ddce53e85437b013671fe7d91a3a1c54f48341
Date: 2025-08-01T20:25:36.785Z
Electron: 35.6.0
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Windows_NT x64 10.0.26100

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by launching a Quarto document containing headings in the reported Positron environment, then compare the outline at launch with its state after switching between source and visual views or editing the file. Done means headings appear in the outline immediately when the document opens, without requiring a toggle or edit.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.