š Bug Report: Subpar layout for some cards when using large system font on mobile
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 61/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- css, rust
- Domain
- accessibility, frontend
Research direction
Start by locating the card layout styles and how Wide UI changes them; reproduce the issue on iOS with Larger Text set around 55%, Card layout selected, and Wide UI enabled. Adjust the layout so cards stack when the available space or enlarged text requires it. Done when the affected cards stack at the reported settings and remain usable on smaller screens.
Written by the indexing model from the issue text.
Description
Describe the bug
Subpar layout for some cards when using large system font on iOS (and probably other devices of the same size).
Steps to reproduce the bug
In iOS, go to Settings ā Display & Text Size ā Larger Text and toggle Larger Accessibility Sizes and set it to around 55%.
In Redlib settings, select the Card layout and toggle Wide UI.
What's the expected behavior?
The layout should be stacked when screen space is limited or font size is large.
Additional context / screenshot
- I checked that the instance that this was reported on is running the latest git commit, or I can reproduce it locally on the latest git commit
- Dominant language
- Rust
- Stars
- 3.9k
- Forks
- 293
- Avg merge
- 14d 8h
- Merged PRs (30d)
- 2
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up ā it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from redlib-org/redlib
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
redlib-org/redlib#604 Ā·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
redlib-org/redlib#571 Ā· 1 comment Ā·
Maintainers usually reply within 3 days
-
š Bug Report: Failed to parse page JSON data: expected value at line 1 column 1 | /r/LivestreamFail/comments/1xd628q/hila_klein_says_ethan_klein_has_been_having_an/.json?Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
redlib-org/redlib#602 Ā· 1 comment Ā·
Maintainers usually reply within 3 days
-
bug
Difficulty 4/5 1-2 days Newbie friendliness 52/100
redlib-org/redlib#600 Ā· 7 comments Ā· 7 reactions Ā·
Maintainers usually reply within 3 days
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
redlib-org/redlib#598 Ā· 22 comments Ā· 18 reactions Ā·
Maintainers usually reply within 3 days
All issues in redlib-org/redlib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dsx-ai-factory/infra-controller#8341 Ā·
Maintainers usually reply within 1 day
-
enhancement triage:deciding
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/otel-arrow#4540 Ā·
Maintainers usually reply within 2 days
-
benchmark: CSV report files contain blank records on WindowsPossibly taken A pull request linked to this issue is open or already merged. Opencomponent:benchmark
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
agentic-os-org/ANOLISA#9177 Ā·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oracle/rust-oracledb#61 Ā·
-
bug priority-medium to-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day