#6351 [GUI] make the default reading size 14 px and give every text role a fixed size table, so nobody has to open Settings
open · @xvcezrqpbxtpzblrt · 0 评论 · 去 GitHub 看
说明
The shipped defaults are small on a wide Windows screen, and most users never open Settings → Reading & focus, so a good default is the only fix that reaches them. Today: `DEFAULT_CONTENT_FS = 12`, `DEFAULT_UI_SCALE = 0.9` (`app/host/src/lib/default-sizes.ts`, owner note "11-01: 12 px and 90%; they were 14 px and 100%"), `DEFAULT_REPLY_WIDTH = 'comfortable'` (`reply-width.ts`) and the reply measure stays `--st-measure: 56ch` (app.css line 54). On a 1440x920 window, paragraphs run at 12 px inside ~30 Chinese characters per line, and tables/code run the full column in the same bubble — one answer has several shapes. I want three defaults changed, plus one stated size table so every role is defined in one place. Proposed defaults: | Setting (Settings > Reading & focus) | Today | Proposed | |---|---|---| | Reading size | 12 px | **14 px** | | Interface size | 90% | **100%** | | Reply width | Comfortable (56ch) | **Full width** | | Role | Size | |---|---| | Body prose (`--st-content-fs`) | 14 px | | h1 / first heading | 17 px | | h2 | 15 px | | h3 and deeper | 14 px | | Tables, code blocks, inline code | 13 px | | Line height for prose | 1.6 (factor, not px) | - 100% interface scale and full width are what I use today after manually changing them, and they read comfortably on a wide screen; the size table is my comfort reference from reading apps I use daily, not a measured result — the maintainer should verify by rendering at 10, 14 and 22 px, as `npm run audit` already does for the measure. - Keep the table as ratios of `--st-content-fs` the way `--st-fs-read-lg` / `--st-fs-read-sm` already do (app.css lines 59, 63): 17/14 = 1.21, 15/14 = 1.07, 13/14 = 0.93, so the Reading size slider scales prose, headings, tables and code together inside the conversation. The interface chrome (buttons, menus, settings rows) follows Interface size as today; this proposal does not change that. - One open question for the ratio table: at the slider's top (22 px), h1 = 22 × 1.21 ≈ 26 px. If that is too large, cap headings at a fixed px, say `min(calc(var(--st-content-fs) * 1.21), 17px)` — your call, I state both paths so the scope stays one change. - `line-height: calc(var(--st-content-fs, 12px) * 1.62)` (app.css line 492) becomes factor 1.6; the current px product grows line height with size, which wastes vertical space at 14 px+. Gaps the table closes (all read from main, marked as static analysis): - `--st-fs-read-lg` = 12 × 1.125 = 13.5 px: headings inside a bubble are smaller than proposed h1/h2, and the rule covers only `h2, h3, h4` (app.css line 7065) — an h1 in a reply has no size rule. - The small ratio has a 12 px floor (app.css line 63), so tables/code cannot drop below 12 px; the proposed table states them directly at 13 px instead of deriving from a floor. - `app.css` carries 12 hardcoded px font-size rules and more live in the other stylesheets (menus, cards, settings rows, onboarding), one of them with `!important` (annotation-fixes.css line 721). They follow Interface size only. The proposal does not touch them — it fixes the conversation type scale; listing them is for scope, not a request to rewrite them. - `ch` measures the "0" glyph (the comment at app.css lines 49–53 notes 56ch ≈ 66–68 Latin characters), so for CJK the comfortable default renders ~30 characters per line. Full width as the default avoids that measure problem for new CJK users; the three named choices and their mechanism stay as shipped. One residual point from #5066 belongs here: Focus reading sizes its column from the same token, but app.css line 469 still caps it at `calc(var(--st-measure) + 72px)` — with 56ch that column does not widen with the Full width setting, and the focus column stays narrow. - Related threads: #5066 (Reply width control, closed by maintainer), #4722 (three widths in one reply, closed), #3818 (selection and newlines, fixed: `Chat.tsx` keeps the view when words are selected, `Markdown.tsx` soft-breaks single newlines, `ui-do-drive.mjs` has a `cases.select` check). This issue adds the size table and the default change those threads did not cover. I am not re-filing them.
Settings → Reading & focus: Reply width = Full width, Reading size = 16–18 px, Interface size = 100%. It works, but every user must find it; the defaults should not require a Settings tour.
Reproduced locally in App 0.2.16 (engine 0.1.62, Windows 11 x64): reading size 12 px and measure 56ch as shipped. The numbers above come from reading `default-sizes.ts`, `reply-width.ts` and `app.css` on main — unconfirmed static analysis where no screenshot is attached.
Scope note: per CONTRIBUTING ("agree the scope in an issue before ... changes to defaults"), this issue is the scope request: one default change (12→14 px) plus one stated size table for conversation text. Not a refactor of UI chrome sizes. Tradeoff: 14 px prose fits less text per screen than 12 px; the maintainer's own 11-01 note shows 14 px was the default before, so this returns to the earlier value with a stated table. When the default moves, `savedSizes` in `default-sizes.ts` needs a decision too: today an unmarked save holding the old default (14 px) is reset to 12 px once (lines 10–17); with 14 as the new default, that rule should be re-checked so existing saves are not silently rewritten.
本站相关内容
相关页面的快捷入口。