Router with view transition api duplicates navigation history sometimes.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by reproducing the intermittent back-navigation failure in the linked SolidRouterVTapiIssue example on Chrome and Brave, including Brave Android if available. Trace the router's view-transition and history handling while repeating A, B, and C navigation; done means back navigation consistently returns to the correct route, including /.
Written by the indexing model from the issue text.
Description
Describe the bug
When you click A, B or C route and then hit back navigation sometimes router navigates back to A even thought it should navigate to /. Its kind of rare behavior, so to repro you have try it multiple times. It happens more frequently on Brave browser than Chrome, so I am not sure what to make of it, maybe its some kind browser issue? Especially since on Brave android, sometimes VT api doesn't even trigger sometimes on back navigation. But my another astrojs site doesn't seem to fail on back navigation with vt api, so i can't be sure.
Your Example Website or App
https://github.com/illispi/SolidRouterVTapiIssue
Steps to Reproduce the Bug or Issue
- Click A
- Click back navigation
- repeat on A, B or C until issue occurs.
Expected behavior
Navigate consistently back to correct route.
Screenshots or Videos
No response
Platform
- Windows 11
- Chrome and Brave 129
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 180
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 19
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 solidjs/solid-router
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
solidjs/solid-router#605 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
solidjs/solid-router#603 · 1 comment ·
-
<A> costs ~6us of server CPU per instance during SSR (20x a plain <a>), mostly mergeProps/splitProps Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
solidjs/solid-router#583 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
solidjs/solid-router#569 · 3 comments ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 38/100
solidjs/solid-router#518 · 2 comments ·
All issues in solidjs/solid-router
Similar issues
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
fix(errors): EHOSTUNREACH from a happy-eyeballs connect is reported as a resolver error (STAMP-80) Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
snapshot-labs/stamp#666 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GauravKarakoti/SecureFlow#1070 · 1 comment ·
-
feature:Languages/Translations good first issue ready Web
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
digitalfabrik/integreat-app#4394 ·