The wizard's body arrives on a step already scrolled (the scroll carries over from the previous step)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- tauri, threejs, typescript, wasm
- Domain
- frontend
Research direction
The wizard body is the .sw-body scroll container shared by every step, so the scroll position from the previous step persists. Find where the step changes in the wizard component and check whether .sw-body is reset there. Reproduce by walking Make → What are you making? → Sign, then Next, and confirm scrollTop is 43 on arrival. Done when each step opens with scrollTop at 0, and the stock step's first line is visible under the pinned header.
Written by the indexing model from the issue text.
Description
The wizard's body arrives on a step already scrolled. Found while regenerating the stock step's baselines for #1259 (picture: docs/design/1259/stock-step-scrolled-on-arrival.png on branch 1259-step2 @ 263211f90).
Walk: Make → What are you making? → Sign, text "Hello" → Next. On the Stock step the wizard body (.sw-body) is at scrollTop = 43 before anything is touched, so the step's first line ("Pick a blank") and the top of the first card sit under the pinned header. The body is the same scroll container for every step, so the scroll left by the previous step (its text field scrolled into view) carries over.
Expected: a step opens at the top. Likely fix: reset the body's scroll when the step changes. Not touched by #1259: the branch's shots show it as it is today.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read 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.
More from SlyWombat/CaseMaker
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
All issues in SlyWombat/CaseMaker
Similar issues
-
parse: child keys like `007`, `1e3`, `0x1f`, `-1` make the parent an empty array and hide the valueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
bketelsen/pi-pocket-team#232 ·
Maintainers usually reply within 1 day
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
wardian-app/Wardian#1746 ·
Maintainers usually reply within 1 day
-
area: interop area: sip-core v3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fonoster/routr#705 · 1 comment ·
Maintainers usually reply within 1 day