Markdown display preferences
The desktop application exposes Font Size and Markdown Headers submenus in the native macOS View menu. Font Size offers 14, 15 (Default), 16, and 17.
AppDelegate.mm validates and persists the selected values in
NSUserDefaults, supplies them as initial properties to every main window,
and posts native change notifications. DesktopWindowManager.mm forwards
those notifications to each observing React root. DesktopRoot.tsx owns the
current in-memory values and supplies them through the shared display
preference provider. A nested theme provider overlays the selected responsive
font-size and line-height preset on the macOS semantic color theme.
MarkdownMessageContent.tsx maps the shared semantic body and H1–H6 metrics to
react-native-markdown-display. Base prose metrics belong on the renderer's
body style; the generic text style must remain color-only because the
library applies it after inherited heading styles. Putting body font metrics
on text makes every heading body-sized. Desktop-specific colors, spacing,
error fallback, inline code, and syntax-highlighted fenced code remain owned
by the desktop renderer.
User-message prose and inline code use bubbleUserText, not
textOnPrimary. The macOS theme builder derives the token from the accent
composited over the effective window background, preserving dark-on-light and
light-on-dark contrast even when the operator uses a custom accent. Plain user
text plus bubble-owned header/footer copy use the same token.
Message, chat, composer, attachment, and metadata styles use responsive theme
tokens. Icons, spacing, and hit targets remain fixed. Desktop panel headers,
connection/session rows, session tabs, and the chat header also consume
semantic typography and color tokens, so the selected display preset and
macOS appearance propagate through the main workspace. Session rows use
normal titles, secondary subtitles/previews, small IDs, and tiny
metadata with matching line heights. Legacy persisted 13 and 19 values migrate
to 14 and 17.
Fenced code passes the semantic code font size and line height plus the macOS
Menlo family directly to react-native-syntax-highlighter; placing those
values only in its customStyle does not affect token text. The application
uses the feature/native-line-height branch of
ferenci84/react-native-syntax-highlighter, whose lockfile entry pins the
reviewable fork commit. Raw and otherwise non-markdown message bodies consume
the semantic message font size and line height.
Static plain message surfaces use React Native Text selectable, including
the raw assistant renderer. React Native paragraph layout owns their complete
height, so these surfaces do not need a nested input scroll view or a
native-to-JavaScript auto-grow event. A production ChatPane XCUITest proves
that the same wheel gesture moves the transcript over both an ordinary
message and the tall raw assistant block.
The chat header title, subtitle, and session ID, each message footer, and the
session status footer use Text selectable. Human verification confirmed
selection works; AppKit also exposes spelling and grammar menu items, which is
accepted for these static fields. Clickable Sessions and home collection rows
retain their separate human gate before any selection change.
Expanded reasoning, tool results, and tool-call arguments use Text
selectable inside their existing bounded ScrollViews. The text measures to
its complete content height while the explicit parent remains the only inner
vertical scroll boundary. Markdown fenced and indented code retain syntax
highlighting but have no nested ScrollView.
Long code wraps to the available message width and the block expands to its
complete content height. Its syntax highlighter uses a selectable root
Text, and wheel input over the block moves the transcript.
MacTextView remains reserved for editable multiline controls that need the
native macOS behavior used by the composer and message editor. Desktop
plugin-provided multiline action fields also use it at a fixed height with
normal Enter-to-insert-newline behavior. Single-line action fields continue to
use React Native TextInput.
Native verification launches DesktopMarkdownGeometryHarness through the
application's harness initial property. The harness uses the production
markdown renderer and reports React onLayout measurements through
DesktopWindowManager because React Native macOS accessibility descendants
are not available to XCTest in this application. MarkdownDisplayMenuUITests
verifies persisted menu values across relaunch, actual Normal/Small heading
geometry, body geometry, and responsive footer geometry.
The Connections panel is expanded by default and its header disclosure
collapses or restores the saved-record list. Up to three records use a
natural-height non-scroll container. Larger sets use a theme-derived
three-row viewport. A non-interactive bottom fade indicates remaining content
and disappears at the real bottom. DesktopConnectionsPanelHarness and
ConnectionsPanelUITests verify natural versus bounded geometry and native
scrolling. Typography and geometry expectations are derived from the active
preset rather than copied point values.
Maintainer entry points:
macos/CrystalLatticeControlDesktopRN-macOS/AppDelegate.mmmacos/CrystalLatticeControlDesktopRN-macOS/DesktopMenuNotifications.hmacos/CrystalLatticeControlDesktopRN-macOS/DesktopWindowManager.mmsrc/DesktopRoot.tsxsrc/chat/MarkdownMessageContent.tsxsrc/testing/DesktopMarkdownGeometryHarness.tsxsrc/testing/DesktopConnectionsPanelHarness.tsxsrc/panels/ConnectionsPanel.tsx__tests__/MarkdownMessageContent.test.tsx__tests__/DesktopMessageBubbleTypography.test.tsmacos/CrystalLatticeControlDesktopRN-macOSUITests/MarkdownDisplayMenuUITests.swiftmacos/CrystalLatticeControlDesktopRN-macOSUITests/ConnectionsPanelUITests.swift