Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Keep Android reader controls usable with large text and resized windows

Open
  • Is something wrong?
#116 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android
Domain
accessibility, mobile, testing

Research direction

Start with the reader layout and typography work in issues #84 and #85, then review the documented font/display scale range and support matrix. Check representative phone and tablet layouts in portrait and landscape, including both interface languages; done means controls remain usable, overflow stays contained, reading position is preserved, and screenshot/layout checks cover these cases.

Written by the indexing model from the issue text.

Description

android difficulty: intermediate enhancement help wanted needs testing

Roadmap: #76

Goal

Support large fonts and changing window sizes in the reader without losing navigation or text.

Acceptance criteria

  • Verify the documented supported font/display scale range and portrait/landscape layouts.
  • Keep project, language, and navigation controls visible and operable when space is constrained.
  • Contain code-block and table overflow within the reader instead of forcing the entire screen wider.
  • Preserve content and reading position when the window resizes.
  • Add screenshot/layout checks for representative phone and tablet sizes in both interface languages.

Start: Reader layout and typography from #84/#85. Record any unsupported size explicitly in the support matrix.

Prerequisites: #84, #85.

Dominant language
Go
Stars
1
Forks
7
Avg merge
1h 45m
Merged PRs (30d)
16

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wavefnd/wave-platform

All issues in wavefnd/wave-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.