@vscode/markdown-editor 0.0.2-6 → 0.0.2-8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vscode/markdown-editor",
-  "version": "0.0.2-6",
+  "version": "0.0.2-8",
   "type": "module",
   "license": "MIT",
   "repository": {
@@ -18,7 +18,8 @@
     "dist",
     "src/view/editor.css",
     "src/view/themes/default.css",
-    "src/view/themes/github.css"
+    "src/view/themes/github.css",
+    "src/view/themes/vscode.css"
   ],
   "exports": {
     ".": {
@@ -31,7 +32,8 @@
     },
     "./editor.css": "./src/view/editor.css",
     "./themes/default.css": "./src/view/themes/default.css",
-    "./themes/github.css": "./src/view/themes/github.css"
+    "./themes/github.css": "./src/view/themes/github.css",
+    "./themes/vscode.css": "./src/view/themes/vscode.css"
   },
   "scripts": {
     "build": "vite build",
@@ -55,9 +57,9 @@
     "@playwright/test": "^1.58.2",
     "@types/katex": "^0.16.8",
     "@types/markdown-it": "^14.1.2",
-    "@vscode/component-explorer": "next",
-    "@vscode/component-explorer-cli": "next",
-    "@vscode/component-explorer-vite-plugin": "next",
+    "@vscode/component-explorer": "0.2.1-59",
+    "@vscode/component-explorer-cli": "0.2.1-60",
+    "@vscode/component-explorer-vite-plugin": "0.2.1-59",
     "@vscode/observables": "workspace:*",
     "github-markdown-css": "^5.9.0",
     "golden-layout": "^2.6.0",
@@ -67,6 +69,7 @@
     "typescript": "^5.7.0",
     "vite": "^6.0.0",
     "vite-plugin-dts": "^4.5.4",
-    "vitest": "^4.1.0"
+    "vitest": "^4.1.0",
+    "zod": "^4.3.6"
   }
 }

package/src/view/editor.css

@@ -12,6 +12,13 @@
  * theme files (`themes/default.css`, `themes/github.css`) applied via the
  * `classNames` editor option; those selectors only ever match inside their
  * own theme class and never style the global scope.
+ *
+ * NO `--vscode-*` variables may be referenced here. This base file must stay
+ * theme-agnostic and know nothing about VS Code. Where a value needs to vary
+ * per theme, expose a local `--md-*` custom property WITH a sensible literal
+ * fallback (e.g. `var(--md-cursor-background, #000)`) and let a theme file set
+ * it. Only `themes/vscode.css` is permitted to read `--vscode-*` variables and
+ * map them onto these `--md-*` properties.
  */
 
 .md-editor {
@@ -44,9 +51,9 @@
 }
 
 .md-block-active {
-	background: #f8f8f8;
+	background: var(--md-block-active-background, #f8f8f8);
 	border-radius: 4px;
-	box-shadow: 0 0 0 8px #f8f8f8;
+	box-shadow: 0 0 0 8px var(--md-block-active-background, #f8f8f8);
 }
 
 /*
@@ -60,6 +67,7 @@
 .md-block-active a {
 	cursor: inherit;
 }
+
 .md-editor.md-mod-down .md-block-active a[href] {
 	cursor: pointer;
 }
@@ -74,6 +82,7 @@
 .md-editor a[href]:hover {
 	text-decoration: underline;
 }
+
 .md-editor:not(.md-mod-down) .md-block-active a[href]:hover {
 	text-decoration: none;
 }
@@ -617,7 +626,7 @@
 .md-cursor {
 	position: absolute;
 	width: 2px;
-	background: #000;
+	background: var(--md-cursor-background, #000);
 	pointer-events: none;
 	animation: md-cursor-blink 1s step-end infinite;
 }

package/src/view/themes/vscode.css

@@ -0,0 +1,331 @@
+/*
+ * VS Code markdown theme.
+ *
+ * A *variable-driven* theme: every color is expressed as `var(--vscode-*, …)`
+ * so the editor adopts whatever VS Code color theme is active (dark, light,
+ * high-contrast, or any custom theme) WITHOUT the editor knowing anything
+ * about VS Code. The editor only references variable NAMES — a documented
+ * contract — and bundles no VS Code CSS.
+ *
+ * Apply it via the editor `classNames` option:
+ *
+ *     new EditorView(model, { classNames: ['md-theme-vscode'] });
+ *
+ * In a real webview VS Code injects the `--vscode-*` custom properties onto
+ * the document root and sets a body theme class, so this theme just works. In
+ * the Component Explorer the same variables are supplied by a snapshot
+ * stylesheet scoped under a `.vscode-theme.<id>` wrapper (see
+ * `fixture/vscodeThemes`). Either way the cascade reaches this theme's rules.
+ *
+ * Fallbacks: each `var()` carries a light-palette fallback so the theme stays
+ * legible even with no `--vscode-*` variables present at all.
+ *
+ * Layout/typography mirrors the GitHub theme (the basis of the production VS
+ * Code markdown editor); only the colors are swapped for variables. Every
+ * selector is scoped under the theme class, so importing this file never
+ * affects the global page or any editor that did not opt in.
+ *
+ * Syntax-token colors are exposed as `--md-tok-*` custom properties (with
+ * light-palette fallbacks). Real VS Code derives token colors from the live
+ * tokenizer's color map (baked in per token), NOT from `--vscode-*`; the
+ * Component Explorer supplies a matching `--md-tok-*` palette per color theme.
+ */
+
+.md-editor.md-theme-vscode {
+    font-family: var(--markdown-font-family, -apple-system, BlinkMacSystemFont,
+            'Segoe WPC', 'Segoe UI', system-ui, 'Ubuntu', 'Droid Sans', sans-serif);
+    font-size: var(--markdown-font-size, 16px);
+    line-height: var(--markdown-line-height, 1.5);
+    color: var(--vscode-editor-foreground, #1f2328);
+    word-wrap: break-word;
+    /*
+     * Active-block highlight (defined theme-agnostically in editor.css) follows
+     * the VS Code surface color so it stays a subtle inset on both light and
+     * dark color themes instead of a fixed light-grey box.
+     */
+    --md-block-active-background: var(--vscode-editorWidget-background, #f8f8f8);
+    /*
+     * Cursor color: editor.css paints `.md-cursor` with `--md-cursor-background`
+     * (theme-agnostic, black fallback); map it to the VS Code cursor color so it
+     * stays visible on dark color themes.
+     */
+    --md-cursor-background: var(--vscode-editorCursor-foreground, #000);
+}
+
+.md-theme-vscode .md-heading {
+    margin-top: 24px;
+    margin-bottom: 16px;
+    font-weight: 600;
+    line-height: 1.25;
+}
+
+.md-theme-vscode h1.md-heading {
+    font-size: 2em;
+    padding-bottom: 0.3em;
+    border-bottom: 1px solid var(--vscode-textSeparator-foreground, #d1d9e0b3);
+}
+
+.md-theme-vscode h2.md-heading {
+    font-size: 1.5em;
+    padding-bottom: 0.3em;
+    border-bottom: 1px solid var(--vscode-textSeparator-foreground, #d1d9e0b3);
+}
+
+.md-theme-vscode h3.md-heading {
+    font-size: 1.25em;
+}
+
+.md-theme-vscode h4.md-heading {
+    font-size: 1em;
+}
+
+.md-theme-vscode h5.md-heading {
+    font-size: 0.875em;
+}
+
+.md-theme-vscode h6.md-heading {
+    font-size: 0.85em;
+    color: var(--vscode-descriptionForeground, #59636e);
+}
+
+.md-theme-vscode .md-paragraph {
+    margin-top: 0;
+    margin-bottom: 16px;
+}
+
+.md-theme-vscode .md-blockquote {
+    margin: 0 0 16px 0;
+    padding: 0 1em;
+    /*
+     * The left padding the `>` gutter hangs in (matches padding-left: 1em at
+     * the base font). Must be an absolute length, not `1em`: the marker
+     * positions itself with this var inside its own (smaller, 0.85em) font
+     * context, so an `em` value would resolve against the marker's font-size
+     * and pull the `>` out of alignment with the text.
+     */
+    --md-blockquote-pad: 16px;
+    color: var(--vscode-descriptionForeground, #59636e);
+    border-left: 0.25em solid var(--vscode-textBlockQuote-border, #d1d9e0);
+}
+
+.md-theme-vscode .md-list {
+    margin-top: 0;
+    margin-bottom: 16px;
+    padding-left: 2em;
+    /* The per-level indentation step the list gutter fills (matches padding-left). */
+    --md-list-indent-step: 2em;
+}
+
+.md-theme-vscode .md-thematic-break {
+    height: 0.25em;
+    padding: 0;
+    margin: 24px 0;
+    background-color: var(--vscode-textSeparator-foreground, #d1d9e0);
+    border: 0;
+}
+
+.md-theme-vscode a {
+    color: var(--vscode-textLink-foreground, #0969da);
+    text-decoration: none;
+}
+
+.md-theme-vscode a:hover {
+    text-decoration: underline;
+}
+
+.md-theme-vscode strong {
+    font-weight: 600;
+}
+
+/* Inline code. */
+.md-theme-vscode :not(pre)>code {
+    font-family: var(--vscode-editor-font-family, ui-monospace, SFMono-Regular,
+            'SF Mono', Menlo, Consolas, 'Liberation Mono', monospace);
+    font-size: 85%;
+    padding: 0.2em 0.4em;
+    margin: 0;
+    color: var(--vscode-textPreformat-foreground, inherit);
+    background-color: var(--vscode-textPreformat-background, #818b981f);
+    border-radius: 6px;
+    white-space: break-spaces;
+}
+
+/* Fenced code block. */
+.md-theme-vscode .md-code-block {
+    margin-top: 0;
+    margin-bottom: 16px;
+    padding: 10px 16px;
+    font-size: 85%;
+    line-height: 1.45;
+    background-color: var(--vscode-textCodeBlock-background, #f6f8fa);
+    border-radius: 6px;
+}
+
+.md-theme-vscode .md-code-block code {
+    font-family: var(--vscode-editor-font-family, ui-monospace, SFMono-Regular,
+            'SF Mono', Menlo, Consolas, 'Liberation Mono', monospace);
+    padding: 0;
+    background-color: transparent;
+    border-radius: 0;
+}
+
+/*
+ * Syntax-highlight token colors. Driven by `--md-tok-*` custom properties so
+ * the explorer (or any embedder) can supply a palette matched to the active
+ * color theme. Fallbacks are the VS Code light theme palette.
+ */
+.md-theme-vscode .md-code-block .tok-keyword {
+    color: var(--md-tok-keyword, #0000ff);
+}
+
+.md-theme-vscode .md-code-block .tok-string {
+    color: var(--md-tok-string, #a31515);
+}
+
+.md-theme-vscode .md-code-block .tok-comment {
+    color: var(--md-tok-comment, #008000);
+}
+
+.md-theme-vscode .md-code-block .tok-number {
+    color: var(--md-tok-number, #098658);
+}
+
+.md-theme-vscode .md-code-block .tok-regexp {
+    color: var(--md-tok-regexp, #811f3f);
+}
+
+.md-theme-vscode .md-code-block .tok-type {
+    color: var(--md-tok-type, #267f99);
+}
+
+.md-theme-vscode .md-code-block .tok-annotation {
+    color: var(--md-tok-annotation, #267f99);
+}
+
+.md-theme-vscode .md-code-block .tok-tag {
+    color: var(--md-tok-tag, #800000);
+}
+
+.md-theme-vscode .md-code-block .tok-attribute {
+    color: var(--md-tok-attribute, #e50000);
+}
+
+.md-theme-vscode .md-code-block .tok-delimiter {
+    color: var(--md-tok-delimiter, inherit);
+}
+
+/*
+ * Display math has no container styling (KaTeX renders it inline-centered).
+ * Keep only the block spacing; horizontal scroll comes from the base sheet.
+ */
+.md-theme-vscode .md-math-block {
+    margin-top: 0;
+    margin-bottom: 16px;
+}
+
+/*
+ * KaTeX renders inline math at 1.21em with its own (larger) line-height, which
+ * would inflate the surrounding line box. Collapse it so the rendered math fits
+ * the text line and the paragraph height stays identical active vs inactive.
+ */
+.md-theme-vscode .md-inline-math .katex {
+    line-height: 1;
+}
+
+.md-theme-vscode .md-table {
+    border-collapse: collapse;
+    margin-top: 0;
+    margin-bottom: 16px;
+    width: auto;
+}
+
+.md-theme-vscode .md-table th,
+.md-theme-vscode .md-table td {
+    padding: 6px 13px;
+    border: 1px solid var(--vscode-editorWidget-border, #d1d9e0);
+    text-align: left;
+}
+
+/*
+ * The editor renders every cell as <td> in a flat <table> of <tr> (no
+ * <thead>/<tbody>/<th>). Row order is: header, delimiter row, body rows.
+ */
+.md-theme-vscode .md-table tr:first-child td {
+    font-weight: 600;
+    padding-top: 11px;
+    padding-bottom: 11px;
+}
+
+/* Active: reclaim the header's extra spacing to host the delimiter row. */
+.md-theme-vscode .md-table.md-block-active tr:first-child td {
+    padding-top: 3px;
+    padding-bottom: 3px;
+}
+
+.md-theme-vscode .md-table tr:nth-child(even):not(.md-table-delimiter-row) {
+    background-color: var(--vscode-textCodeBlock-background, #f6f8fa);
+}
+
+/*
+ * The delimiter row (`| --- | --- |`) is editor source shown only while
+ * editing; render it borderless with no vertical padding so it occupies just
+ * the compact 10px reclaimed from the header.
+ */
+.md-theme-vscode .md-table-delimiter-row td {
+    border: 0;
+    padding: 0 13px;
+    background: transparent;
+}
+
+/*
+ * Active table: the source `|` pipes ARE the outline. Drop the HTML cell
+ * borders (kept as transparent so the 1px box geometry — and thus the table's
+ * height and first-text X — is unchanged) and clear the zebra fill so the
+ * table reads as plain source.
+ */
+.md-theme-vscode .md-table.md-block-active td {
+    border-color: transparent;
+}
+
+.md-theme-vscode .md-table.md-block-active tr:nth-child(even):not(.md-table-delimiter-row) td {
+    background-color: transparent;
+}
+
+/*
+ * Shift each cell's leading pipe onto its left gridline (where the border was)
+ * and the last cell's closing pipe onto the right gridline. `position:
+ * relative` moves only the painted glyph by the cell's horizontal padding;
+ * siblings and the glue's reserved width are untouched, so active/inactive
+ * height and first-text X stay pixel-identical.
+ */
+.md-theme-vscode .md-table.md-block-active td>.md-glue-tableCellGlue:first-child,
+.md-theme-vscode .md-table.md-block-active .md-table-delimiter-row td>.md-marker-tableDelimiter {
+    position: relative;
+    left: -13px;
+}
+
+/*
+ * The last cell's closing `|` floats right after the (left-aligned) cell text.
+ * Pin it to the column's right gridline (the cell's border edge, 13px past the
+ * content box) so the right outline is a straight line.
+ */
+.md-theme-vscode .md-table.md-block-active td:last-child {
+    position: relative;
+}
+
+.md-theme-vscode .md-table.md-block-active td:last-child>.md-glue-tableCellGlue:last-child {
+    position: absolute;
+    right: 0;
+    top: 0;
+}
+
+/*
+ * The delimiter row's last cell carries its closing `|` as a separate
+ * `tableDelimiterClose` marker; pin it to the same right gridline as the body
+ * rows' closing pipe so the last column's outline stays straight.
+ */
+.md-theme-vscode .md-table.md-block-active .md-table-delimiter-row td:last-child>.md-marker-tableDelimiterClose {
+    position: absolute;
+    right: 0;
+    top: 0;
+}