Overlapping Text and Layout Issues in Featured Items on Mobile (iPhone 11–13)
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
- typescript
- Domain
- frontend, mobile-dev
Research direction
Start by reproducing the issue at https://beta.dataverse.org/spa/ on a 390 x 664 viewport and inspect the Featured Items section in the frontend. Compare the first card on iPhone 11–13 with the reported modern iPhone behavior; done means text no longer overlaps, padding and line height remain usable, and card content stays within its bounds.
Written by the indexing model from the issue text.
Description
Environment:
Device Models Affected: iPhone 11, iPhone 12, iPhone 13
OS: iOS 15.6
Browser: Chrome & Safari (via BrowserStack real device)
URL: https://beta.dataverse.org/spa/
Branch: develop
Build: Current deployed build on beta.dataverse.org
Viewport: 390 x 664 px
Description:
On smaller iPhone models (iPhone 11, 12, 13), the homepage's Featured Items section displays overlapping text, broken line breaks, and excessive card expansion. Text from multiple layers of content seems to stack on top of each other, making it unreadable and negatively impacting the layout.
Steps to Reproduce:
Open https://beta.dataverse.org/spa/ on an iPhone 13 (or 11/12) using Chrome.
Scroll down to the “Featured Items” section.
Observe the text rendering within the first featured item card.
Expected Behavior:
The featured item cards should:
Maintain proper padding and line height
Avoid text overlap
Render content within the card’s bounds with ellipsis or controlled height
Actual Behavior:
Headline and body text overflow into each other
Multiple layers of text appear visually stacked
Card height expands beyond intended size with no scroll or truncation
Screenshot attached
Note: Everything looks good in the more modern Iphones
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Contributor 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 IQSS/dataverse-frontend
-
bug Size: 3 SPA
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
IQSS/dataverse-frontend#1041 · 1 comment · 3 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
IQSS/dataverse-frontend#1001 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
IQSS/dataverse-frontend#1073 · 1 comment ·
-
Size: 30 SPA
Difficulty 4/5 3-5 days Newbie friendliness 38/100
IQSS/dataverse-frontend#1069 ·
-
Size: 30 SPA
IQSS/dataverse-frontend#1064 · 1 assignee ·
All issues in IQSS/dataverse-frontend
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·