[ui] Page scrolls horizontally at 375px — ParsedHeader's control row overflows by ~67px
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- playwright, typescript
- Domain
- frontend, mobile-dev, testing-qa
Research direction
Start at ParsedHeader's div.flex.items-center.gap-3 control row and run the mobile-375 Playwright project against / with a parsed résumé. Verify the control row no longer enlarges document.documentElement.scrollWidth at 375px across every corpus fixture, and add the assertion under e2e/mobile/**.
Written by the indexing model from the issue text.
Description
/ has horizontal scroll at 375px with nothing open: document.documentElement.scrollWidth 435–442 vs clientWidth 375.
Attribution (measured, not guessed)
First noticed in #959 as "separately observed — NOT attributed". It has since been pinned down twice, independently:
- Measured across six corpus fixtures at six viewport widths during #960: the overflow is present at 375px for every résumé, on unmodified code, and absent from 640px up (scrollWidth == clientWidth exactly at 640/767/768/1024/1280).
- The overflowing node is
ParsedHeader'sdiv.flex.items-center.gap-3— the "Feedback / Save to library / Try another file" control row — reachingright: 442.1.
Explicitly not the score strip: the docked strip's own row measures width 285, scrollWidth 285 at 375px in all three verdict bands, and #960's flex-nowrap + shrink-0 change introduced no new horizontal overflow (verified at 375/640/767/768/1024/1280).
Why it is worth its own issue
It is a real mobile defect — a page that scrolls sideways on a phone — and it has already distorted two other pieces of work: #959's original analysis attributed part of its popover bug to a wrap that the page overflow made look worse, and #960 had to gate the verdict word below sm specifically to avoid adding a second cause to an overflow it did not create. Fixing this may let that gating relax (CollapsedScoreBar's docblock says so).
Acceptance criteria
-
scrollWidth == clientWidthat 375px on/with a parsed résumé, for every corpus fixture. - The control row wraps or scrolls internally rather than overflowing the page.
- Covered by an assertion in the
mobile-375Playwright project (e2e/mobile/**), which exists as of #954/#960.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 4
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 45
Getting set up
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 offlinecv/OfflineCV
-
refactor testing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
improvement ux:job-search
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
All issues in offlinecv/OfflineCV
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
diegosouzapw/OmniRoute#14869 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
Maintainers usually reply within 1 day
-
status: waiting triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
freeCodeCamp/freeCodeCamp#70412 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability untriaged
Difficulty 1/5 Under an hour Newbie friendliness 88/100
opensearch-project/OpenSearch-Dashboards#12816 ·
Maintainers usually reply within 1 day