aboutsummaryrefslogtreecommitdiffstats
path: root/src/api.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-09-13 08:10:02 -0700
committerAdam Soltys <[email protected]>2026-09-13 08:10:02 -0700
commit9fb2154236a3f9d7ede5344cfcc4fa56ff3ada0c (patch)
tree4317e098a84d62d628337560b3e629c7550ea369 /src/api.js
parentfae3468590d9e7627e855f6b5636b116d6582f3d (diff)
downloadcoinosv3-9fb2154236a3f9d7ede5344cfcc4fa56ff3ada0c.tar.gz
coinosv3-9fb2154236a3f9d7ede5344cfcc4fa56ff3ada0c.zip
Posts and messages get a reading size.
A feed of posts was set in .small — 13px, the size used for captions and row subtitles. On a phone it read like footnotes. Measured against Amethyst on the same Pixel 9, side by side: its note body renders a line pitch of 62 device pixels, ours 50. Post bodies get their own class at 16px, which is Amethyst's own default for a note body, and chat and DM bubbles move 15 → 16 to match; the names and inbox previews above them keep pace. New line pitch measured on the phone: 60 against Amethyst's 62. A quoted note inside a post stays a step smaller, since it's context rather than the post you're reading. Worth recording for whoever reads this next: this phone has the Android font scale at 1.15. Amethyst uses sp and honours that automatically; CSS px in a TWA does not, and there's no way for a page to read that setting. So Amethyst will still render about 15% larger than us on this device no matter what we pick. Matching its DEFAULT is the target that makes sense for everyone else. chat-layout-test had rotted (onboarding copy, .header-msgs now matching the settings button, a screenshot path from another machine's scratch dir) — repaired, and it's what proves the composer still fits at the larger size, on all three viewports. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_019mrt228Upn9nNCwGixzSLx
Diffstat (limited to 'src/api.js')
0 files changed, 0 insertions, 0 deletions