uxml-preview 0.6.1 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,255 @@
 # Changelog
 
+## 0.7.0 — 2026-10-21
+
+Unity's runtime theme, by default. A preview of a game screen now looks like the
+game: the values come from a real runtime panel (PanelSettings + UIDocument in
+Play mode) on Unity 6.3, and the editor theme stays one option away.
+
+### Behavior changes
+
+- **The default theme is `'runtime'`.** `render`, `resolveStyles` and
+  `layoutDocument` take `theme: 'runtime' | 'editor'`; `RenderResult.theme`
+  says which was drawn. Without the option, every render changes:
+  - text: 14px, colour #1b1b1b (editor: 12px, #d2d2d2)
+  - Label: margin 4 4 2 2, padding 4 2 4 1 (editor: 0; 0 2 0 1)
+  - Button: margin 2 4, padding 10 12, border 1 #959595, background #bcbcbc,
+    radius 0 (editor: margin 1 3, padding 1 6, border 1 #303030 with a
+    #242424 bottom, background #585858, radius 3, text #eeeeee)
+  - a scrolling ScrollView reserves 24px for its scroller (editor: 13px)
+  - the core paints nothing behind the panel, as Unity paints nothing behind
+    a runtime panel. Runtime text is dark: a host drawing on a dark backdrop
+    has to supply one. Pass `theme: 'editor'` for the 0.6.x drawing plus the
+    values below.
+- **Both themes now carry their measured values**, where 0.6.x had only the
+  Button margin and text alignment: panel text size and colour (inherited by
+  every element, origin `builtin-theme`), Label padding, Button padding,
+  border, colours and `:hover` / `:active` / `:focus` / `:disabled` colours.
+- **Label and Button do not shrink** (`flex-shrink: 0`, measured on both
+  themes). `inventory`'s `ItemDesc` now lands where Unity puts it.
+- **Only the element written `enabled="false"` is dimmed.** Unity gives that
+  element `unity-disabled` and opacity 0.5 and leaves its descendants at 1; a
+  disabled button inside a disabled panel was 0.25 here. A `disabled` forced
+  through `states` does not dim at all (see "A state forced through `states`
+  stays on that element" below).
+- **The runtime theme paints CJK without kinsoku**, as Unity's runtime panel
+  does. The editor theme keeps the browser's line breaking (a known
+  difference at one 60px Chinese case, Unity 6.3 editor).
+- An unknown `theme` value warns (`malformed`, reason `invalid-value`) and
+  draws the default.
+- **Applying the theme is no longer a warning.** "Built-in control defaults
+  applied, as measured on Unity <version>" and "<ScrollView> drawn with built-in
+  child elements measured on Unity <version>" are gone: a measured theme value
+  is not a difference from Unity, and both were measured the same on
+  6000.0.40f1 and 6.3. `version-dependent` now comes only from values the dumps
+  show differ by version, both on the editor theme:
+  - a Button with no text: 4px high on 6000.0.40f1, 19px on 6000.3.25f1 (the
+    editor theme draws 6000.0.40f1's)
+  - letter- or word-spacing with no `-unity-text-generator`: the editor theme's
+    default generator is standard on 6000.0.40f1 and advanced on 6000.3.25f1
+    (drawn as advanced)
+  - a GroupBox whose `text` is only spaces: its title is 0px high on 6000.0.40f1
+    and 15px on 6000.3.25f1 (advanced generator; drawn as 15). Under an explicit
+    standard generator both versions measure 0 and nothing is warned. The runtime
+    theme draws that title 0px high on both versions, unwarned. The same holds for
+    a Label or Button whose text is only spaces (Label 0px vs 15px, Button 4px
+    vs 19px; the runtime theme draws the text 0px high)
+  A host that keyed anything off the removed warnings loses that signal.
+- **Text is measured by its generator's rules.** The runtime theme resolves
+  `-unity-text-generator: standard`, as Unity's runtime panel does on both
+  versions; the editor theme resolves advanced (the 6.3 editor's default). The
+  resolved value — not the theme — now picks the rules, measured on the text
+  cohort: Standard text is `floor(fs·r + (n−1)·fs·lineHeight/pointSize) + 1`
+  high (r = (ascent − descent) / pointSize) and measured and painted without
+  kerning (`font-kerning: none`); Advanced keeps `ceil(n·fs·r)` and kerning.
+  On the runtime theme a whole-number line height gains 1px, later lines
+  advance by `lineHeight`, and kerned pairs (Jua's English, 2–4px) widen. An
+  author's `-unity-text-generator: standard` on the editor theme measures the
+  same way. `textHeight` takes the generator as an optional sixth argument
+  (advanced when left out).
+- **A text wider than the width it is offered is clipped to it**, as Unity
+  does (measured, `g-clamp`, both versions and themes): in a row, in a column
+  with `align-items: flex-start`, with or without `overflow: hidden`. An
+  absolutely placed text and a TextField's inner text are not clipped, as in
+  Unity. A long no-wrap Label in a narrow box now has the box's width instead
+  of overflowing it. No accuracy figure moved. The same holds for the height
+  (`g-clamp-h`): a text offered a smaller height is clipped to it, down to its
+  padding and border — a TextField's inner text included.
+- **A focused TextField's label takes the focus colour** (runtime #00526a,
+  editor #81b4ff), as Toggle and RadioButton labels do.
+
+### New controls
+
+- **GroupBox and Box are drawn** instead of falling back with an
+  `unsupported-control` warning (bundle B). GroupBox builds Unity's title
+  Label before its children when it has `text` (a part named
+  `unity-group-box__label`, reachable from author USS by that class); Box
+  carries its border and background. Both match the `c07-GroupBox` and
+  `c07-Box` dumps on both themes.
+- **TextField is drawn** (bundle C): single-line and multiline, placeholder,
+  password (the mask only; the value never reaches the DOM), disabled, with or
+  without a label. It builds Unity's parts — the label (`unity-text-field__label`),
+  `#unity-text-input`, the multiline container and the inner text
+  (`unity-text-element--inner-input-field-component`) — which author USS reaches
+  by Unity's names. Matches the 6.3 `c07-TextField`, `c-textfield` and
+  `c-textfield-hook` dumps on both themes. The caret, the selection and editing
+  are not drawn. A host that counted TextField's `unsupported-control` warning
+  loses it.
+- **Toggle and RadioButton are drawn** (bundle E): label, text, checked
+  (`value="true"`), disabled. Checked is the `:checked` state on the control and
+  its input part, as in Unity; the radio checkmark appears only when checked.
+  The check mark is this preview's drawing (Unity's textures cannot be loaded).
+- **A state forced through `states` stays on that element.** Measured
+  (e-disabled, both versions): a forced `disabled` neither dims (no
+  `unity-disabled`) nor reaches the element's parts or children; forced
+  hover/focus/active do not reach parts either. 0.7.0's earlier handling dimmed
+  a forced-disabled element at 0.5 (an inference, now reversed).
+  `enabled="false"` still disables the whole subtree and dims once.
+- **Slider and SliderInt are drawn** (bundle D): label, input, drag container,
+  tracker, dragger and its border, and with `show-input-field` a TextField
+  showing the value. The dragger sits where Unity puts it for any value —
+  t = clamp((value - low) / (high - low), 0, 1) along the drag container less
+  the dragger, upward for `direction="Vertical"` — measured in eleven steps
+  both ways, a range, a reversed range and an out-of-range value. Dragging is
+  not drawn. A host that used Slider as its example of an unsupported
+  control loses that example.
+- **ProgressBar, TextElement and RepeatButton are drawn** (bundle F).
+  ProgressBar builds Unity's container, background, bar and title; the bar
+  width follows Unity's rule, floor(background width - 2) x clamp(value) /
+  high-value, measured on fourteen values, ranges and widths. On the editor
+  theme a bar at or below low-value warns `version-dependent` (1px on
+  6000.0.40f1, 0 on 6.3; drawn as 6.3). TextElement and RepeatButton are plain
+  text, as in Unity — a RepeatButton does not look like a button. A host that
+  counted their `unsupported-control` warnings loses them.
+- **The editor theme's Toggle box is drawn** (E2): Unity draws it from a
+  built-in texture; the preview paints it in colours measured off Unity's
+  screen, so an unchecked Toggle no longer disappears on the editor theme.
+
+### Classes
+
+- **Every drawn control carries Unity's classes**, parts included (A2, held by
+  `tests/contract-070/classes.test.ts` against every 0.7.0 dump). Label and
+  Button gain `unity-text-element`, so an author rule on that class now reaches
+  them as it does in Unity. ScrollView gains `unity-scroll-view--scroll` and a
+  `mode` class (`--vertical`, `--horizontal`, `--vertical-horizontal`), and its
+  three parts their `unity-scroll-view__*` classes. Classes only: no coordinate
+  moved. The scrollers inside a ScrollView are still not built.
+
+### Review fixes (adversarial review, 2026-10-21)
+
+Each found by the review or while fixing it, measured on Unity where Unity
+decides it, and pinned (`tests/contract-070/review-*.test.ts`,
+`c1-nowrap.test.ts`, `n3-part-fonts.test.ts`, and in a real browser
+`tests/text-cohort/paint-r15.mjs`, now part of `pnpm test:text`).
+
+- **A Label or Button does not wrap unless the author says so.** Unity
+  resolves `white-space: nowrap` on both; the theme sheets now give it to
+  `.unity-label` and `.unity-button`. A long label in a narrow column is one
+  clipped line, as in Unity, not several. TextElement and RepeatButton still
+  wrap.
+- **Text is painted where it was measured.** A line break (`
+`) is a painted
+  line whatever the `white-space`; the painted line height is the measured
+  advance (Standard `lineHeight`, Advanced ascent − descent); kerning follows
+  each text's own generator; `pre-wrap` keeps runs of spaces when it wraps.
+- **A wrapping text is as wide as Unity makes it.** The editor theme
+  (Advanced) takes its longest line; the runtime theme (Standard) takes the
+  width up to the last glyph that fit where a line broke — the line, its space
+  and the start of the next word — floor + 1. Both used to take the longest
+  line. Measured on probes that use each sentence once (`r1w-wrap`,
+  `r1w-wrap2`): 22 of 24 texts match, two are known differences (below).
+- **A word longer than the line breaks between characters**, Latin and Hangul,
+  measured and painted, in a TextElement, a Label with `white-space: normal`
+  and a multiline TextField (`r1w-long`, both versions and themes). It used to
+  overflow the line as one piece. See Corrections.
+- **A TextField keeps runs of spaces in its value**, measured and painted.
+- **An author font reaches a control's part text** (field labels, the
+  TextField's text, GroupBox and ProgressBar titles), as Unity draws them.
+- **Attribute values are read as Unity reads them:** booleans ignore case
+  (`"True"`; `"1"` is not true), `direction` ignores case, `inverted` mirrors a
+  slider, SliderInt takes whole numbers, a value that is not a number falls back
+  to the default and is warned (`malformed`, `invalid-value`), `Infinity` is
+  clamped, the old names `text=` and `maskCharacter=` work.
+- **ProgressBar:** the fill is `width × clamp(value, low, high) / high` (it was
+  empty whenever the value was at low).
+- **Text edges:** absolutely placed text is not wrapped; an empty TextField is
+  clipped like one with a value; a multiline TextField's text keeps its
+  wrapped height in a fixed-height field.
+- **States:** a forced `disabled` no longer matches `:enabled`; a state USS
+  does not have (`:selected`) is warned and not applied; a forced `:checked`
+  reaches the input part and draws the check mark.
+- **Author rules beat the painter's stand-ins** for the editor check box
+  (background, radius, tint).
+- **Warnings that were missing:** a non-px `font-size`; an unknown
+  `-unity-text-generator` (the theme's generator stands); an inherited author
+  generator no longer reads as "drawn as advanced"; a host font without a
+  FaceInfo under the Standard generator; a FaceInfo with no usable
+  `pointSize`.
+- **Yoga nodes are freed when layout throws** (a host measure function that
+  throws used to leave the tree allocated).
+
+### Accuracy — previous and new figures
+
+| Set | 0.6.1 | 0.7.0 | Why |
+|---|---:|---:|---|
+| Runtime theme coordinates (Unity 6.3 runtime panel) | — | 1122 / 1148 | new set (662/676 on the original 40 cases); the settings screen adds 472 values and 12 text-width mismatches; the 26 left are the editor set's known divergences |
+| Editor theme coordinates (Unity 6000.0.40f1) | 660 / 676 | 1122 / 1148 | Label `flex-shrink: 0` (`ItemDesc` y, height) gave 662/676; the settings screen (two cases, all 15 drawn controls) adds 472 values, 12 of them the footer's text widths |
+| Template cohort | 215 / 220 | 215 / 220 | unchanged; G3-4 text-width deltas moved by the Label padding |
+| Text cohort, editor (Chromium vs Unity) | 92/92 · 84/92 · 92/92 · 157/159 | unchanged | |
+| Text cohort, runtime panel (new set) | — | 92/92 · 84/92 · 92/92 · 159/159 (both versions) | measured with the Standard rules (before them: 60/92 heights, 89/92 widths); the 8 plain heights left are Inter's Hangul fallback rows, as on the editor; `noto-jp-zh-20-w60` (203 vs 201) is a fallback glyph starting the last line, a known difference. None unexplained |
+
+Every Unity baseline is now a solo dump, each probe or case in its own Unity
+process: under the Standard text generator a text's width depends on what the
+same process drew before (0-2px). The inventory's nine text-metric values moved
+by 1px on Unity's side (291/93 -> 292/92), still counted as mismatches.
+
+The acceptance screen (`settings`, `settings-ko`: every drawn control on one
+screen, design section 6) is in both golden sets, and a contract test judges
+the same screen with Unity's own text sizes (the dump's `MeasureTextSize`, or
+Unity's layout width where that is 1-2px wider): every box and part matches but
+one half-pixel title. It checks the boxes given the text sizes, not the text
+widths (`docs/accuracy.md`).
+
+### Known differences
+
+- Scrollbars reserve their width and are not drawn.
+- Half-pixel rounding: a centred text whose position falls on a half pixel is
+  rounded up by Unity and down by this preview (a ProgressBar title, 1px in x).
+  Decided after measuring per alignment.
+- A glyph the given font does not have, starting the last line: the runtime
+  preview's box can be taller than Unity's (2px in the measured pair). The text
+  cohort's `noto-jp-zh-20-w60` is this case: Noto Sans JP has no `张`, Unity draws
+  it with a fallback font, 201 against the Standard rule's 203. Thirteen probes
+  dumped alone (`tests/text-cohort/fallback-zh/`) show the 2px only when the
+  fallback glyph starts the last line. Not reproduced: the preview does not know
+  a font's glyph coverage.
+- Unity side: on the runtime panel, writing the same text earlier in a
+  document with a different wrap setting makes a later copy of it shorter.
+  Not reproduced.
+- The editor theme's kinsoku (one 60px Chinese case on the 6.3 editor).
+- The runtime theme's wrapping width, in two of 24 measured texts: a Korean
+  sentence in 100px is 4px wider than Unity's 83 (Unity takes its longest line
+  there), and a 10px sentence 2px wider than Unity's 77. Heights match.
+
+### For consumers
+
+`docs/design/0.7.0-handoff.md` lists what changes, every consumer task, and the
+classified failures of the consumers' own tests against this core:
+vscode-uxml-preview 4 (1 already on 0.6.1, 3 using a now-drawn control as the
+unsupported example), uxml-author 32 (17 already on 0.6.1; 3 such examples, 1
+`version-dependent` sample that no longer warns, 11 skill-document lists and
+"cannot draw" sentences).
+
+### Corrections
+
+- `white-space: pre` does not wrap to the width in Unity either. 0.6.0 said it
+  did, from evidence that could not tell the two apart (`pre-wrap2`).
+- 0.6.1's "a Korean or Latin word wider than the box is not split" was
+  inferred, not measured: none of the cohort's cases had a word wider than its
+  box. Measured, Unity breaks a word longer than the line between characters
+  (`r1w-wrap2`, `r1w-long`, both versions and themes), and the preview now
+  follows it.
+
 ## 0.6.1 — 2026-10-16
 
 Japanese and Chinese text, first. The Japanese and Simplified Chinese READMEs

package/README.ja.md

@@ -5,6 +5,8 @@
 **Unity UI Toolkit の UXML/USS を、Unity エディタなしでブラウザ上に描画します。レイアウトには
 UI Toolkit 自身が使用する Yoga エンジンを採用し、描画結果は実際の Unity と突き合わせて検証しています。**
 
+![uxml-preview 0.7.0：左に UXML・USS で書いた設定画面、右にブラウザで描画した結果](https://raw.githubusercontent.com/ReuHomi/uxml-preview/main/docs/media/promo-0.7.0.gif)
+
 [![プレイグラウンド画面：上部にプレビュー画面、下部に各警告の理由と Unity 側の実際の挙動を表示](https://raw.githubusercontent.com/ReuHomi/uxml-preview/main/docs/media/playground.png)](https://reuhomi.github.io/uxml-preview/)
 
 ### ▶ [プレイグラウンドを開く](https://reuhomi.github.io/uxml-preview/)
@@ -18,8 +20,11 @@ UI Toolkit 自身が使用する Yoga エンジンを採用し、描画結果は
 
 ## 検証方法
 
-- **座標：** 完成画面1件を含む40個のレイアウトケースにおいて、要素の座標値 660 / 676 が Unity 6000.0.40f1 と一致しています。[すべての差異とその内訳 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md) 同じケースを Unity 6.3（6000.3.25f1）で再ダンプしたところ、同日に取得した 6000.0.40f1 のダンプとすべての配置が一致しました。[6.3 での再測定 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#unity-63-lts-re-measurement-2026-10-15)
-- **テキスト：** 実際のブラウザで描画し、Unity 6000.3.25f1 と Label 単位で比較しました。行数 92 / 92、高さ 84 / 92、幅 92 / 92（誤差 1px または 1% 以内）。高さが異なるケースはすべて、ハングルを含まない欧文フォント Inter で韓国語、または韓国語と欧文が混在するテキストを指定したものです。Unity はこれをフォールバックフォントで描画しますが、本プレビューではまさにその状況を警告として通知します。[テキスト検証セット →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#text-cohort-separate-set-measured-2026-10-16)
+- **座標・ランタイムテーマ（既定）：** 同じ42個のレイアウトケースにおいて、要素の座標値 1122 / 1148 が実際の Unity 6.3 ランタイムパネル（6000.3.25f1、PanelSettings + UIDocument、Play モード）と一致しています。残る差異はすべてエディターテーマにもあるものです。[測定方法 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#runtime-theme-separate-set-measured-2026-10-17)
+- **座標・エディターテーマ：** 完成画面3件（インベントリ、描画する15種のコントロールをすべて使った設定画面の英語版・韓国語版）を含む42個のレイアウトケースにおいて、要素の座標値 1122 / 1148 が Unity 6000.0.40f1 と一致しています。[すべての差異とその内訳 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md) 同じケースを Unity 6.3（6000.3.25f1）で再ダンプしたところ、同日に取得した 6000.0.40f1 のダンプとすべての配置が一致しました。[6.3 での再測定 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#unity-63-lts-re-measurement-2026-10-15)
+- **テキスト、ランタイムテーマ（既定）：** 実際のブラウザで描画し、実際の Unity ランタイムパネル（6000.0.40f1 と 6000.3.25f1、プローブごとに別の Unity プロセス）と Label 単位で比較しました。行数 92 / 92、高さ 84 / 92、幅 92 / 92（誤差 1px または 1% 以内）、ボックス境界での改行ケース 159 / 159。高さが異なるケースはすべて、ハングルを含まない欧文フォント Inter で韓国語、または韓国語と欧文が混在するテキストを指定したものです。Unity はこれをフォールバックフォントで描画しますが、本プレビューではまさにその状況を警告として通知します。[ランタイムのテキストセット →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#runtime-panel-separate-set-measured-2026-10-19--item-t)
+- **テキスト、エディターテーマ：** 同じ 92 個の Label を Unity 6000.3.25f1 のエディターと比較 — 92 / 92、84 / 92、92 / 92、改行ケース 157 / 159（残る 2 件：中国語 1 ケースでのエディターの禁則処理と、ボックス境界での 1px の自然幅の差）。[テキスト検証セット →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#text-cohort-separate-set-measured-2026-10-16)
+- **測定条件：** 座標の数値は、テキストサイズを与えたときのレイアウトを測っています（ハーネスはテキストを固定関数で測り、テキスト計測はテキストの数値が別に測ります）。テキストの数値は Unity と同じフォントファイルを渡した条件での値です。フォントを渡さない場合はブラウザーの既定フォントで測るため、文字幅が数 px 異なり、複数行のテキストでは行数が変わることがあります。[条件 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md)
 - **Unity バージョン：** 基準バージョンは Unity 6.3 LTS です。USS プロパティかどうかの判定は Unity 公式のプロパティ一覧（6.6 まで）に基づいており、6.7 は LTS になるまでサポート対象外です。[サポート範囲 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/supported.en.md)
 - **一致しない箇所は見過ごさず、警告として報告します。** 未サポートのコントロール・プロパティ・値は、その理由とともに（測定済みの場合は Unity 側が代わりにどう振る舞うかも含めて）警告として返されます。[警告について →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/api.en.md#warnings)
 

package/README.ko.md

@@ -5,6 +5,8 @@
 **Unity UI Toolkit의 UXML/USS를 Unity 에디터 없이 브라우저에서 그립니다. 배치는 UI Toolkit이
 쓰는 엔진인 Yoga가 하고, 결과는 Unity와 대조해 측정했습니다.**
 
+![uxml-preview 0.7.0: 왼쪽에 UXML·USS로 쓴 설정 화면, 오른쪽에 브라우저가 그린 결과](https://raw.githubusercontent.com/ReuHomi/uxml-preview/main/docs/media/promo-0.7.0.gif)
+
 [![놀이터 화면: 위에는 화면, 아래에는 경고마다 이유와 Unity가 대신 하는 일](https://raw.githubusercontent.com/ReuHomi/uxml-preview/main/docs/media/playground.png)](https://reuhomi.github.io/uxml-preview/)
 
 ### ▶ [놀이터 열기](https://reuhomi.github.io/uxml-preview/)
@@ -18,8 +20,11 @@
 
 ## 어떻게 확인했나
 
-- **좌표:** 완성된 화면 하나를 포함한 배치 케이스 40개에서, 요소 좌표 값 660 / 676이 Unity 6000.0.40f1과 같습니다. [다른 곳은 전부 이름을 붙여 적었습니다 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md) 같은 케이스를 Unity 6.3(6000.3.25f1)에서 다시 덤프했더니, 같은 날 다시 뜬 6000.0.40f1 덤프와 배치가 모두 같았습니다. [6.3 재측정 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md#unity-63-lts-재측정-2026-10-15)
-- **텍스트:** 실제 브라우저에서 그려 Unity 6000.3.25f1과 Label 단위로 대조했습니다. 줄 수 92 / 92, 높이 84 / 92, 너비 92 / 92(1px 또는 1% 이내). 높이가 다른 것은 모두 라틴 글꼴 Inter로 쓴 한글·혼합 문장입니다 — Inter에 한글이 없어 Unity가 대체 폰트로 그리고, 미리보기는 바로 그 경우에 경고합니다. [텍스트 코호트 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md#텍스트-코호트-별도-검증-세트-2026-10-16-측정)
+- **좌표, 런타임 테마(기본값):** 같은 배치 케이스 42개에서 요소 좌표 값 1122 / 1148이 실제 Unity 6.3 런타임 패널(6000.3.25f1, PanelSettings + UIDocument, Play 모드)과 같습니다. 남은 차이는 모두 에디터 테마에도 있는 것입니다. [어떻게 쟀나 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md#런타임-테마-별도-세트-2026-10-17-측정)
+- **좌표, 에디터 테마:** 완성된 화면 셋(인벤토리, 그리는 컨트롤 15종을 모두 쓴 설정 화면의 영어·한국어판)을 포함한 배치 케이스 42개에서, 요소 좌표 값 1122 / 1148이 Unity 6000.0.40f1과 같습니다. [다른 곳은 전부 이름을 붙여 적었습니다 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md) 같은 케이스를 Unity 6.3(6000.3.25f1)에서 다시 덤프했더니, 같은 날 다시 뜬 6000.0.40f1 덤프와 배치가 모두 같았습니다. [6.3 재측정 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md#unity-63-lts-재측정-2026-10-15)
+- **텍스트, 런타임 테마(기본):** 실제 브라우저에서 그려 실제 Unity 런타임 패널(6000.0.40f1과 6000.3.25f1, 프로브마다 따로 띄운 Unity)과 Label 단위로 대조했습니다. 줄 수 92 / 92, 높이 84 / 92, 너비 92 / 92(1px 또는 1% 이내), 상자 경계의 줄바꿈 케이스 159 / 159. 높이가 다른 것은 모두 라틴 글꼴 Inter로 쓴 한글·혼합 문장입니다 — Inter에 한글이 없어 Unity가 대체 폰트로 그리고, 미리보기는 바로 그 경우에 경고합니다. [런타임 텍스트 세트 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md#런타임-패널-별도-세트-2026-10-19-측정--항목-t)
+- **텍스트, 에디터 테마:** 같은 92개 Label을 Unity 6000.3.25f1 에디터와 대조 — 92 / 92, 84 / 92, 92 / 92, 줄바꿈 케이스 157 / 159(남은 둘: 중국어 한 케이스의 에디터 금칙, 상자 경계에서 1px 다른 자연 폭). [텍스트 코호트 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md#텍스트-코호트-별도-검증-세트-2026-10-16-측정)
+- **어떤 조건에서 쟀나:** 좌표 수치는 글 크기가 주어졌을 때의 배치를 잽니다 — 하네스는 글을 고정 함수로 재고, 글 측정은 텍스트 수치가 따로 잽니다. 텍스트 수치는 Unity와 같은 글꼴 파일을 넘겨준 조건에서 잰 값입니다. 글꼴을 넘기지 않으면 브라우저 기본 글꼴로 재며, 글자 폭이 몇 px 다르고 여러 줄 글의 줄 수가 달라질 수 있습니다. [조건 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.md)
 - **Unity 버전:** 기준은 Unity 6.3 LTS입니다. USS 속성인지는 Unity 공식 속성표(6.6까지)로 판정하고, 6.7은 LTS가 나올 때까지 지원하지 않습니다. [지원 범위 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/supported.md)
 - **맞지 않는 곳은 조용히 넘기지 않고 경고로 알립니다.** 지원하지 않는 컨트롤·속성·값은 이유와 함께, 측정한 경우에는 Unity가 대신 어떻게 하는지까지 경고로 돌아옵니다. [경고 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/api.md#경고)
 

package/README.md

@@ -5,6 +5,8 @@
 **Render Unity UI Toolkit UXML/USS in a browser, without the Unity Editor — laid
 out by Yoga, the engine UI Toolkit itself uses, and measured against Unity.**
 
+![uxml-preview 0.7.0: a settings screen written in UXML and USS on the left, drawn in the browser on the right](https://raw.githubusercontent.com/ReuHomi/uxml-preview/main/docs/media/promo-0.7.0.gif)
+
 [![The playground: a screen, and under it each warning with its reason and what Unity does instead](https://raw.githubusercontent.com/ReuHomi/uxml-preview/main/docs/media/playground.png)](https://reuhomi.github.io/uxml-preview/)
 
 ### ▶ [Open the playground](https://reuhomi.github.io/uxml-preview/)
@@ -18,8 +20,11 @@ all runs in the page.
 
 ## How it is verified
 
-- **Coordinates:** 660 / 676 element coordinate values identical to Unity 6000.0.40f1, over 40 layout cases including a complete screen. [Every difference, named →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md) Re-dumped on Unity 6.3 (6000.3.25f1), every one of those cases laid out exactly as in a 6000.0.40f1 dump taken the same day. [The 6.3 re-measurement →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#unity-63-lts-re-measurement-2026-10-15)
-- **Text:** drawn in a real browser and compared with Unity 6000.3.25f1 Label by Label — line count 92 / 92, height 84 / 92, width 92 / 92 within 1px or 1%. Every height that differs is Korean or mixed text set in Inter, a Latin font with no Hangul, which Unity draws with a fallback font; the preview warns about exactly that. [The text cohort →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#text-cohort-separate-set-measured-2026-10-16)
+- **Coordinates, runtime theme (the default):** 1122 / 1148 element coordinate values identical to a real Unity 6.3 runtime panel (6000.3.25f1, PanelSettings + UIDocument in Play mode), over the same 42 layout cases. Every value left over is one the editor theme also has. [How it was measured →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#runtime-theme-separate-set-measured-2026-10-17)
+- **Coordinates, editor theme:** 1122 / 1148 element coordinate values identical to Unity 6000.0.40f1, over 42 layout cases including three complete screens (an inventory, and a settings screen with all 15 drawn controls, in English and Korean). [Every difference, named →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md) Re-dumped on Unity 6.3 (6000.3.25f1), every one of those cases laid out exactly as in a 6000.0.40f1 dump taken the same day. [The 6.3 re-measurement →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#unity-63-lts-re-measurement-2026-10-15)
+- **Text, runtime theme (the default):** drawn in a real browser and compared Label by Label with a real Unity runtime panel (6000.0.40f1 and 6000.3.25f1, each probe in its own Unity process) — line count 92 / 92, height 84 / 92, width 92 / 92 within 1px or 1%, and 159 / 159 line-break cases at box edges. Every height that differs is Korean or mixed text set in Inter, a Latin font with no Hangul, which Unity draws with a fallback font; the preview warns about exactly that. [The runtime text set →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#runtime-panel-separate-set-measured-2026-10-19--item-t)
+- **Text, editor theme:** the same 92 Labels against Unity 6000.3.25f1's editor — 92 / 92, 84 / 92, 92 / 92, and 157 / 159 line-break cases (the two left: the editor's kinsoku in one Chinese case, and a 1px natural width at a box edge). [The text cohort →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#text-cohort-separate-set-measured-2026-10-16)
+- **Under what conditions:** the coordinate figures measure layout given the text sizes — the harness measures text with a fixed function, and the text figures measure text separately. The text figures are measured with the same font file Unity uses passed to the preview; without a font, the preview measures with the browser's default font, so text widths can differ by a few pixels and wrapped text can break into a different number of lines. [Conditions →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md)
 - **Unity version:** the reference is Unity 6.3 LTS. A property is USS if Unity's official property table lists it, up to 6.6; 6.7 is not supported until it is an LTS. [What is supported →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/supported.en.md)
 - **What does not match is reported, not glossed over.** An unsupported control, property or value comes back as a warning that says why, and — where it was measured — what Unity does instead. [Warnings →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/api.en.md#warnings)
 

package/README.zh-CN.md

@@ -5,6 +5,8 @@
 **无需 Unity 编辑器，即可在浏览器中渲染 Unity UI Toolkit 的 UXML/USS——由 UI Toolkit 自身使用的
 Yoga 引擎负责布局，并与 Unity 实测结果进行了比对验证。**
 
+![uxml-preview 0.7.0：左侧是用 UXML 和 USS 编写的设置界面，右侧是浏览器中的渲染结果](https://raw.githubusercontent.com/ReuHomi/uxml-preview/main/docs/media/promo-0.7.0.gif)
+
 [![在线体验页面：上方为预览画面，下方列出每条警告的原因及 Unity 的实际处理方式](https://raw.githubusercontent.com/ReuHomi/uxml-preview/main/docs/media/playground.png)](https://reuhomi.github.io/uxml-preview/)
 
 ### ▶ [打开在线体验 (Playground)](https://reuhomi.github.io/uxml-preview/)
@@ -18,8 +20,11 @@ Yoga 引擎负责布局，并与 Unity 实测结果进行了比对验证。**
 
 ## 验证方式
 
-- **坐标：** 在包含完整界面在内的 40 个布局用例中，660 / 676 个元素坐标值与 Unity 6000.0.40f1 完全一致。[查看全部差异明细 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md) 在 Unity 6.3（6000.3.25f1）中重新导出这批用例后，所有布局结果均与当天导出的 6000.0.40f1 结果一致。[6.3 重新测量结果 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#unity-63-lts-re-measurement-2026-10-15)
-- **文本：** 在真实浏览器中绘制，并与 Unity 6000.3.25f1 逐个 Label 进行比对——行数 92 / 92、高度 84 / 92、宽度 92 / 92（误差在 1px 或 1% 以内）。所有高度存在差异的用例，均是使用了不含韩文字符的拉丁字体 Inter 来排版韩文或混排文本；此时 Unity 会改用回退字体绘制，而本预览工具会针对该情况发出明确警告。[文本测试集 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#text-cohort-separate-set-measured-2026-10-16)
+- **坐标·运行时主题（默认）：** 在同样的 42 个布局用例中，1122 / 1148 个元素坐标值与真实的 Unity 6.3 运行时面板（6000.3.25f1，PanelSettings + UIDocument，Play 模式）完全一致。剩余差异均为编辑器主题同样存在的差异。[测量方法 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#runtime-theme-separate-set-measured-2026-10-17)
+- **坐标·编辑器主题：** 在包含三个完整界面（物品栏，以及使用全部 15 种已绘制控件的设置界面英文版和韩文版）在内的 42 个布局用例中，1122 / 1148 个元素坐标值与 Unity 6000.0.40f1 完全一致。[查看全部差异明细 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md) 在 Unity 6.3（6000.3.25f1）中重新导出这批用例后，所有布局结果均与当天导出的 6000.0.40f1 结果一致。[6.3 重新测量结果 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#unity-63-lts-re-measurement-2026-10-15)
+- **文本，运行时主题（默认）：** 在真实浏览器中绘制，并与真实的 Unity 运行时面板（6000.0.40f1 与 6000.3.25f1，每个探针单独启动一个 Unity 进程）逐个 Label 进行比对——行数 92 / 92、高度 84 / 92、宽度 92 / 92（误差在 1px 或 1% 以内），框边界处的换行用例 159 / 159。所有高度存在差异的用例，均是使用了不含韩文字符的拉丁字体 Inter 来排版韩文或混排文本；此时 Unity 会改用回退字体绘制，而本预览工具会针对该情况发出明确警告。[运行时文本测试集 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#runtime-panel-separate-set-measured-2026-10-19--item-t)
+- **文本，编辑器主题：** 同样的 92 个 Label 与 Unity 6000.3.25f1 编辑器比对——92 / 92、84 / 92、92 / 92，换行用例 157 / 159（其余 2 个：一个中文用例中编辑器的禁则处理，以及框边界处 1px 的自然宽度差）。[文本测试集 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md#text-cohort-separate-set-measured-2026-10-16)
+- **测量条件：** 坐标数值测量的是给定文字尺寸时的布局（测试工具用固定函数测量文字，文字测量由文本数值单独衡量）。文本数值是在向预览传入与 Unity 相同的字体文件的条件下测得的。若不传入字体，预览会用浏览器默认字体测量，文字宽度可能相差几个像素，多行文本的行数也可能不同。[条件 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/accuracy.en.md)
 - **Unity 版本：** 基准版本为 Unity 6.3 LTS。某项属性是否属于 USS，依据 Unity 官方属性表（截至 6.6）判定；6.7 在推出 LTS 版本之前暂不支持。[支持范围 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/supported.en.md)
 - **不一致之处会明确报告，绝不静默忽略。** 遇到不支持的控件、属性或值时，工具会返回警告并说明原因；对于已实测的情况，还会一并告知 Unity 的实际处理方式。[警告说明 →](https://github.com/ReuHomi/uxml-preview/blob/main/docs/api.en.md#warnings)
 

package/dist/controls/registry.d.ts

@@ -1,4 +1,16 @@
 import { ElementNode } from '../model/types';
+export declare function uxmlBoolean(value: string | undefined): boolean | undefined;
+export declare function isVertical(value: string | undefined): boolean;
+/**
+ * Purpose: match k-slider/k-progress dumps (bundle-A plan §32) for display and layout.
+ * Ensures: values are finite and clamped; invalid input retains the attribute default.
+ */
+export declare function numericControlValue(node: ElementNode): {
+    low: number;
+    high: number;
+    value: number;
+    invalid: boolean;
+};
 /**
  * An element a control builds for itself, which the file never mentions.
  *
@@ -11,8 +23,18 @@ import { ElementNode } from '../model/types';
  * observed in `tests/golden/unity/scrollview-*.json`, not invented.
  */
 export interface ControlPart {
-    /** Unity's name, e.g. `unity-content-viewport`. */
+    /** Unity name, or class identity for the unnamed GroupBox title. */
     name: string;
+    /** Earlier part index, or null for the owner; omitted preserves the wrapper chain. */
+    parent?: number | null;
+    textValue?: string;
+    /** Text parts are measured leaves; a leading Label is a sibling of the wrapper chain. */
+    kind?: 'leading-text' | 'text';
+    /** Attribute text is decoded only for the derived rendering, never in the AST. */
+    textAttribute?: 'text' | 'label' | 'value' | 'title';
+    typeName?: string;
+    unnamed?: boolean;
+    classes?: readonly string[];
     /**
      * USS this part always carries, because the control fixes it.
      *
@@ -26,10 +48,14 @@ export interface ControlSpec {
     /** Renders the `text` attribute as its own content. */
     hasText: boolean;
     /**
-     * Elements the control inserts between itself and the file's children,
-     * outermost first. The file's children go inside the last one.
+     * Parts are parent-before-child. Explicit parent indices describe branches.
+     * Otherwise these are elements inserted between the control and file children,
+     * outermost first. File children go inside the last wrapper; leading text
+     * parts are siblings before them and exist only for non-empty owner text.
      */
     parts: readonly ControlPart[];
+    /** File children follow all parts; omitted uses the last non-text part, or owner. */
+    fileChildrenHost?: 'owner' | 'last-part';
     /**
      * USS classes Unity's own constructor puts on this control, which the theme
      * stylesheet then targets. Not in the `class` attribute and not in the model:
@@ -58,10 +84,12 @@ export declare function resolveControl(node: ElementNode): ResolvedControl;
 export declare function isRoot(node: ElementNode): boolean;
 /**
  * Purpose:      the USS classes Unity would have added to this element.
- * Ensures:      empty for anything with no renderer of its own — a fallback box
- *               must not pick up theme styling meant for a control we do not
- *               actually draw.
+ * Ensures:      control classes and own disabled class remain outside the model.
  */
 export declare function implicitClassesOf(node: ElementNode): readonly string[];
 /** Controls with a renderer of their own. Everything else still draws. */
 export declare function supportedControlNames(): string[];
+/** Ensures: password values are masked before measurement or DOM painting. */
+export declare function partTextOf(node: ElementNode, part: ControlPart): string | undefined;
+/** Ensures: legacy wrapper chains and explicit part trees share one parent contract. */
+export declare function partParentIndex(parts: readonly ControlPart[], index: number): number | null;

package/dist/controls/theme.d.ts

@@ -1,87 +1,63 @@
 /**
  * Unity's control defaults, as far as we have measured them.
  *
- * Unity ships a theme stylesheet that gives controls their own margin, padding
- * and border before any author USS runs. This renderer supplied none of it, so
- * every Button sat 3px left and 1px high of where Unity puts it — invisible on
- * one button and compounding across a row.
- *
- * **Only measured values live here.** Every declaration below was derived from
- * a Unity layout dump in tests/golden/unity/, and adding `Button`'s margin
- * moved all five Button cases from 18 mismatched values to zero. Values read
- * from Unity's source instead would look identical in this file while being
- * wrong in a way no test could see: they would not appear in the unmeasured
- * list, so they would quietly pass for ground truth.
- *
- * Two kinds of measurement feed this file, and the second was a long time
- * coming. Geometry comes from the coordinate dumps. `-unity-text-align` cannot:
- * where a glyph sits inside a box does not move the box, so no dump can ever
- * see it. It came from the Step 6 eye check — Unity centres a Button's label
- * and this renderer had it at the top left, which is visible the moment the two
- * screenshots sit side by side and invisible in 368 compared numbers.
- *
- * `opacity` on `:disabled` came from the same screenshots, but by sampling
- * pixels rather than looking. Unity's disabled Drop button is rgb(41,50,67);
- * the base colour rgb(58,74,104) composited at half over the footer's
- * rgb(24,26,31) is (41, 50, 67.5) — all three channels exact. That arithmetic
- * is the evidence, and it is why the value is 0.5 and not a number that merely
- * looked about right.
- *
- * Getting there took two wrong turns worth recording. First the author's
- * `Button:disabled` rule was blamed for not applying — it genuinely does not,
- * because `#DropButton` outranks it, in both engines. Then Unity was accused of
- * ranking state rules above specificity, and `state-vs-id` and `state-vs-inline`
- * refuted that: Unity answers 40 to both, exactly as this cascade already did.
- * The dimming was never about the cascade at all.
- *
- * What is deliberately absent, and why:
- *
- *   - `Label` — measured, and it has no default margin. `inherit-vs-direct`
- *     puts an explicitly-sized Label at the origin of a sized parent, and Unity
- *     reports x=0 y=0. Nothing to add is a result, not an omission.
- *   - padding, border, font — invisible to the cases we have. Every compared
- *     element is explicitly sized, and USS is border-box, so padding and border
- *     do not move the outer rectangle. They are unmeasured, so they are not here.
- *   - `Label`'s text alignment — the eye check could not separate it from the
- *     box at this size. Unmeasured, so absent.
- *
- * The class names were a separate claim from the values, and are now measured
- * too. `unity-button` came from Unity's documented `Button.ussClassName`, which
- * the margin dumps said nothing about — they proved the spacing, not the
- * selector delivering it. The golden case `theme-class-hook` was written to
- * settle exactly that, and Unity answered on 2026-08-05: a `.unity-button` rule
- * in author USS reaches a bare `<ui:Button>`, sizing it 120×40 in both engines.
- * The selector below is therefore measured, not assumed.
- */
-/** Where every value in this file was measured. Theme values move between versions. */
-export declare const THEME_UNITY_VERSION = "6000.0.40f1";
-/**
- * Parsed once and spliced in ahead of author sheets, so an author rule of equal
- * specificity wins on order — which is how a theme stylesheet behaves in Unity.
- *
- * Class selectors rather than type selectors, also for Unity's reasons: a theme
- * rule at `.unity-button` (0,1,0) beats an author's `Button { }` (0,0,1), and
- * that is a real Unity gotcha worth reproducing rather than smoothing over.
+ * Unity supplies control spacing before author USS runs; omitting it once put
+ * every Button 3px left and 1px high, compounding across a row. Only measured
+ * values live here. Values copied from Unity's source could look just as
+ * authoritative while being wrong without appearing in the unmeasured list.
+ *
+ * There are two measured themes: editor in an EditorWindow on 6000.0.40f1
+ * (tests/layout/unity/6000.0.40f1/probe-editor-070/), runtime on a real runtime
+ * panel on 6000.3.25f1 (tests/layout/unity/6000.3.25f1/probe-panel/), with
+ * identical runtime values on 6000.0.40f1. Geometry comes from coordinate dumps.
+ * `-unity-text-align` came from the Step 6 eye check: a glyph's position inside
+ * its box does not move the box, so 368 matching coordinates could not reveal
+ * that Unity centred Button text while this renderer put it at the top left.
+ *
+ * Opacity 0.5 was established by pixel arithmetic: Unity's disabled Drop button
+ * is rgb(41,50,67); its base rgb(58,74,104) composited at half over the footer's
+ * rgb(24,26,31) gives (41,50,67.5). It is measured, not chosen by appearance.
+ * `nested-disabled` now places it on `.unity-disabled`, which Unity adds only
+ * where enabled="false" was written. This replaces the earlier `:disabled`
+ * rule that applied half opacity at every disabled level and dimmed twice.
+ *
+ * Two wrong turns preceded that result. The author's `Button:disabled` rule
+ * was first blamed for not applying, but `#DropButton` outranks it in both
+ * engines. Then state rules were thought to outrank specificity; `state-vs-id`
+ * and `state-vs-inline` both returned 40 in Unity, refuting that explanation.
+ * The dimming was never a cascade defect.
+ *
+ * Earlier omissions, superseded by c07-existing and c07-states:
+ * - "Label has nothing" described only its measured editor margin; Label and
+ *   Button spacing and flex-shrink are now measured for both themes.
+ * - "Padding, border, font deliberately absent" is superseded by measured
+ *   padding, borders, colours and font size; Label text alignment stays absent.
+ *
+ * Class hooks are a separate claim from values: margin dumps proved spacing,
+ * not the selector delivering it. `unity-button` began with the documented
+ * Button.ussClassName; `theme-class-hook` then confirmed on 2026-08-05 that
+ * author `.unity-button` reaches a bare <ui:Button>, sizing it 120×40 in Unity
+ * and this renderer. The hook is measured, not assumed.
  */
-export declare const THEME_USS = ":disabled {\n  opacity: 0.5;\n}\n\n.unity-button {\n  margin: 1px 3px;\n  -unity-text-align: middle-center;\n}\n";
+export type Theme = 'runtime' | 'editor';
+export declare const DEFAULT_THEME: Theme;
+/** Unity version used to measure the editor theme. */
+export declare const THEME_UNITY_VERSION: string;
+/** Unity measurement version for each theme. */
+export declare const THEME_UNITY_VERSIONS: Readonly<Record<Theme, string>>;
+/** Panel defaults inherited by the rendered elements. */
+export declare const PANEL_TEXT_DEFAULTS_SELECTOR = "UXML";
 /**
- * **Unmeasured, and reachable: nested disabled elements.**
- *
- * `enabled="false"` puts a whole subtree into `:disabled` — measured, by
- * `disabled-inherits`. The rule above therefore hands every level its own
- * `opacity: 0.5`, and CSS multiplies them, so a disabled button inside a
- * disabled panel comes out at a quarter. Unity almost certainly dims once.
- *
- * Not guessed at, because the fix has a choice inside it — dim only where
- * `enabled="false"` was written, or suppress the inherited one — and picking
- * without evidence is how the `.unity-button` selector became a hypothesis
- * nobody noticed for a day. Opacity leaves no trace in a coordinate dump, so
- * settling it needs a screenshot of a nested case. Recorded in
- * `docs/backlog.md` and visible in `visual-nested-disabled`.
+ * Editor theme stylesheet; kept as the legacy editor-sheet export.
+ * Parsed once and spliced in ahead of author sheets, so equal specificity lets
+ * author rules win on order, as in Unity. Class selectors also preserve Unity's
+ * specificity: `.unity-button` (0,1,0) beats an author `Button {}` (0,0,1).
  */
+export declare const THEME_USS: string;
+export declare const THEME_SHEETS: Readonly<Record<Theme, string>>;
 /**
  * Purpose:      how much width a vertical scrollbar claims, given whether it shows.
  * Ensures:      0 when the content fits — Unity hides the scroller rather than
  *               shrinking the viewport for a bar nobody can see.
  */
-export declare function verticalScrollbarWidth(overflows: boolean): number;
+export declare function verticalScrollbarWidth(overflows: boolean, theme?: Theme): number;