Saving in Markdown preview mode corrupts bold+inline-code formatting (**/` backtick order)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Now, to be clear. It may be switching between preview / markdown mode. This is the first time it’s happened (it happened to me twice during the session).

Editing a Markdown file in preview mode and saving can corrupt inline formatting where bold and backticks are combined. On save, the ** and backtick delimiters get reordered, so text like access becomes broken variants such as access**, **access**, or **access.

The file content is changed on disk even though the intent was normal preview editing. The corruption is easy to miss because preview may still look roughly correct, but the raw source no longer renders bold monospace for API field names.

Steps to Reproduce

  1. Open a Markdown file (e.g. spec.md) containing bold+inline-code patterns like access, router.rules[], providerId.
  2. Open preview mode (or split editor with preview).
  3. Edit content while in preview.
  4. Save the file (Cmd+S).
  5. Inspect the raw Markdown source or git diff.

Expected: formatting unchanged after save.
Actual: ** and backticks are reordered. Example:

Before:

  • access and router.rules[]

After save:

  • access** and **router.rules[]

Operating System

MacOS

Version Information

Version: 3.6.31 (Universal)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Thanks for the report @NgNiji! One of our devs noticed this too. When strong and code marks share a span, the serializer emits the wrong delimiter order. Hopefully, we can get this fixed up!