Product description expands beyond screen width and becomes unclickable in Enatega app

Open

#864 opened on Jul 22, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: javascript, react-native
Domain: mobile

Research direction

Start by reproducing the issue on an Android device in the Enatega app: open the store, expand a product description, and inspect the layout when the content exceeds the screen width. Find the store product-description expansion entry point and verify that the full description stays within the visible boundaries and remains clickable.

Written by the indexing model from the issue text.

Description

Describe the bug
In the Enatega application store, when clicking on the arrow down button to expand and view the complete description, the content overflows beyond the screen limit on the right side, making part of it unclickable.

To Reproduce
Steps to reproduce the behavior:

Open the Enatega app on an Android device.
Navigate to the store section.
Click on the arrow down button to expand the product description.
Observe that the expanded content exceeds the screen width on the right and becomes unclickable.
Expected behavior
The expanded description should remain within the visible screen boundaries, ensuring that all content is viewable and interactable.

Smartphone (please complete the following information):

Device: Samsung A15

OS: Android

Additional context
This may be caused by missing responsive styles or improper layout handling when content expands. Needs fixing to ensure mobile usability and accessibility.

Dominant language: JavaScript
Stars: 2
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the 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.