hotwired / hotwired/hotwire-native-android
`refresh_historical_location` does not use current WebView location after form submission on modal bottom sheet
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 163
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hi !
This is a follow-up on #122. There is this situation we found where the issue of the refresh on the initial URL instead of the new one still persists. It happens after form submission that redirects to /refresh_historical_location inside a modal bottom sheet. In this situation, the modal gets dismissed and the page behind it gets refreshed but with the "old" URL.
I made a fork of the demo app to make a reproducible example of the issue.
Thanks!
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.
Research direction
Start with the reproducible demo app linked in the issue and reproduce the form submission that redirects to /refresh_historical_location inside a modal bottom sheet. Trace how the modal dismissal refreshes the page and compare the current WebView location with the initial URL; done means the refresh uses the redirected location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100