Microsoft/vscode

Syntax highlighting randomly breaks in inlineSuggest preview

Open

#234,963 opened on Dec 2, 2024

View on GitHub
 (0 comments) (1 reaction) (1 assignee)TypeScript (10,221 forks)batch import
bugghost-texthelp wantedinline-completions

Repository metrics

Stars
 (74,848 stars)
PR merge metrics
 (Avg merge 11h 43m) (1,000 merged PRs in 30d)

Description

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.95.3
  • OS Version: Windows 11

Steps to Reproduce:

  1. Enable editor.suggest.preview and editor.inlineSuggest.syntaxHighlightingEnabled
  2. Create JSON file with snippet
  3. ctrl+space inside ""
  4. Scroll down to captures and notice that it highlights correctly ✅ Image
  5. Scroll down to beginCaptures and notice that it highlights incorrectly ❌ Image
  6. Also notice that holding down shift changes the syntax highlighting ❌ Image
  7. Also also notice that the position of the real " (undimmed double quote) moves around ❌
{
    "$schema": "https://raw.githubusercontent.com/RedCMD/TmLanguage-Syntax-Highlighter/main/vscode.tmLanguage.schema.json",
    "patterns": [
        {
            ""
        }
    ]
}

Contributor guide

Research direction
Investigate the inlineSuggest preview component and its syntax highlighting logic. Look for race conditions or state mismatches when scrolling or interacting with the preview.
Tech stack
typescript
Domain
frontenddeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
TypeScriptVS Code extension development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50