### Describe the bug Given a URL with both search parameters and a hash fragment, unsetting the search params results in navigation to "/", losing any existing path/route. The linked example does not actually run properly in the playground, but you can copy it to repro locally. ### Your Example Website or App https://playground.solidjs.com/developerdizzle/2f1f4876-fb97-4ce3-bede-d0e23e93b663 ### Steps to Reproduce the Bug or Issue 1. Navigate to a route with a querystring param and hash fragment, e.g.: `/demo?foo=bar#test` 2. Call `setSearchParams({ foo: "" })` 3. Notice the URL has changed to `/#test` The bug does not happen if no hash fragment exists ### Expected behavior The existing route/path is maintained ### Screenshots or Videos https://github.com/user-attachments/assets/feea89f6-d0c5-48af-8f86-616a3d61678f ### Platform - OS: Linux Mint - Browser: Chrome - Version: 150.0.7871.46 ### Additional context _No response_
Describe the bug
Given a URL with both search parameters and a hash fragment, unsetting the search params results in navigation to "/", losing any existing path/route.
The linked example does not actually run properly in the playground, but you can copy it to repro locally.
Your Example Website or App
https://playground.solidjs.com/developerdizzle/2f1f4876-fb97-4ce3-bede-d0e23e93b663
Steps to Reproduce the Bug or Issue
/demo?foo=bar#testsetSearchParams({ foo: "" })/#testThe bug does not happen if no hash fragment exists
Expected behavior
The existing route/path is maintained
Screenshots or Videos
solidjsrouterbug.mp4
Platform
Additional context
No response