DimensionDev / DimensionDev/Flare

[UI/UX] Long post text is truncated in full-screen media viewer without scrolling or expansion option

Open
#2,549 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
1.5k
Forks
67
Avg merge
11h 8m
Merged PRs (30d)
84

Description

Summary

In the full-screen media preview mode (when viewing images or videos), the text overlay at the bottom is limited to a fixed height/number of lines and gets truncated if the post is lengthy. Users are currently unable to read the full text without dismissing the media viewer and returning to the post detail view.

Environment

• Device: iPhone Air
• OS Version: iOS 26.7
• App Version: Flare 1.7.5 (1750)

Reproduction Steps
  1. Open a post that contains both media (image/video) and a relatively long text body (e.g., > 4–5 lines).
  2. Tap the media to enter the full-screen media viewer.
  3. Observe the caption/text overlay displayed at the bottom.
Observed Behavior

The text is truncated after 3–4 lines (ending with ... or clipped off). There is no way to scroll through the text, tap to expand, or reveal the remaining post content within the viewer. Users must exit the media viewer to read the full post in the detail view, which interrupts the media browsing flow.

Image Image
Proposed Solutions / Expected Behavior

It would be great to have an interaction to view the complete text without having to exit the viewer:

  1. Swipe-up / Expandable Bottom Sheet (Recommended): Support dragging up on the bottom overlay (or tapping on it) to expand into an iOS-style Bottom Sheet (half-screen / full-screen drawer). This allows users to read the full content and scroll comfortably, then swipe down to dismiss while keeping the media viewer open.
  2. Scrollable Text Container / Inline Expansion: Alternatively, make the bottom text overlay container vertically scrollable if the content overflows, or provide a "Show more" / "Expand" toggle button that extends the caption area.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the issue in the full-screen media viewer with a post containing more than 4–5 lines of text, then locate the viewer's text overlay implementation. Done means the complete post text can be read within the viewer through scrolling or expansion, without dismissing the media view.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.