Skip to content

[Bug]: iOS chat text does not follow Dynamic Type larger text settings #97534

Description

@jmcte

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The iOS chat UI uses fixed point fonts for assistant message text and composer text, so chat text does not reliably follow the user's iOS Larger Text / Dynamic Type setting.

Scope

This issue is intentionally scoped to chat text only:

  • apps/shared/OpenClawKit/Sources/OpenClawChatUI/ChatMessageViews.swift
  • apps/shared/OpenClawKit/Sources/OpenClawChatUI/ChatView.swift
  • apps/shared/OpenClawKit/Sources/OpenClawChatUI/ChatComposer.swift

Do not use this issue to refactor Settings, sidebar, Talk tab, command-center cards, app chrome, or other dense iOS layout surfaces.

Steps to reproduce

  1. On an iPhone, enable a larger text size in iOS Settings > Accessibility > Display & Text Size > Larger Text.
  2. Open the OpenClaw iOS app.
  3. Open the Chat surface and view assistant message text.
  4. Type into the chat composer.

Expected behavior

Chat message text and composer text should scale with the user's Dynamic Type / Larger Text setting while remaining readable and usable.

Actual behavior

Inspection of current source shows chat text uses fixed point fonts in the shared chat UI:

  • Assistant message text builds Font.system(size: 14) in ChatMessageViews.swift.
  • The chat intro card uses .font(.system(size: 15)) in ChatView.swift.
  • The iOS composer TextField uses .font(.system(size: 15)) in ChatComposer.swift.

These fixed sizes can keep chat text visually small even when the user has enlarged iOS text.

OpenClaw version

Current main source inspected on 2026-06-28.

Operating system

iOS with Larger Text / Dynamic Type enabled.

Install method

Native iOS app.

Model

N/A: native iOS UI rendering issue.

Provider / routing chain

N/A: native iOS UI rendering issue.

Additional provider/model setup details

N/A.

Logs, screenshots, and evidence

Relevant source evidence from current checkout:

apps/shared/OpenClawKit/Sources/OpenClawChatUI/ChatMessageViews.swift
  ChatAssistantTextBody builds assistant/thinking text with Font.system(size: 14).

apps/shared/OpenClawKit/Sources/OpenClawChatUI/ChatView.swift
  ChatAssistantIntroCard uses .font(.system(size: 15)).

apps/shared/OpenClawKit/Sources/OpenClawChatUI/ChatComposer.swift
  iOS TextField composer uses .font(.system(size: 15)).

Impact and severity

Affected: iOS users who rely on Larger Text / Dynamic Type for readable chat.

Severity: Accessibility/usability bug for the primary chat workflow.

Frequency: Expected whenever the affected chat text paths render with fixed font sizes under larger system text settings.

Consequence: Chat responses and composer input can remain harder to read than the user's system accessibility preference implies.

Additional information

Likely fix direction: replace fixed chat text sizes with semantic Dynamic Type styles such as .body, .callout, or Font.system(.body, design: ...), and verify Chat message rendering plus composer input at accessibility text sizes. Keep the fix limited to chat text for this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions