Skip to content

Make message typography and contrast configurable #28

Description

@mamoru

Important

This preserved product issue is now part of the fresh MIT replacement program. Final implementation owner: atrinik/client. Legacy C/SDL2, packet, global-state, and file-path details below are historical evidence only.

Replacement implementation contract

Preserve user-selectable font attributes. Consume semantic colors and global UI scaling; define bounded font/size/weight/line-spacing choices, previews, accessibility-safe defaults, and migrations rather than per-popup styling.

New implementation and tests are independent MIT work unless an exact contribution by a person in the approved MIT provenance-grantor registry is admitted through the recorded file-level grant and complete-history policy. Preserve every player-facing, accessibility, disclosure, and performance design decision below.

Required verification

  • Test pure state/geometry/material/UI behavior headlessly where possible and run supported Linux/Windows integration paths.
  • Add bounded malformed, stale, lifecycle, resource-loss, and recovery cases appropriate to the owner.
  • Add shared Go/Rust protocol fixtures for authoritative fields; presentation never reconstructs hidden rules.
  • Use released shared renderer/protocol/toolkit contracts and wrapper-managed replacement scenarios.
Preserved product/design specification and historical implementation notes

Currently, when a message window pops up (such as the "/help" window), the font
size is teensy-tiny and non-adjustable by the user. The user should be able to
select the font settings used in message and pop-up windows. Currently, the
user is only able to change the font SIZE used in the chat windows.

Font size, colour, etc. should be user-selectable. Another example as to why,
using "/help" window, the LINK text currently shows up as blue text on an
orange-ish background -- horrible contrast, so makes reading the links (the
actual commands that are in the help file) QUITE difficult.

Reported by NiteStar. Atrinik Bugzilla 183

Metadata

Metadata

Assignees

No one assigned

    Fields

    Priority

    None yet

    Start date

    None yet

    Target date

    None yet

    Effort

    None yet

    Projects

    Status
    Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions