-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hx-push-url does not include GET parameters #58
Comments
Yep, looks like a bug. |
Some kind of hack but you can set the server response header |
1cg
pushed a commit
that referenced
this issue
Jun 10, 2020
Fixed w/ a65c37e |
strangeRabbit777
added a commit
to strangeRabbit777/high-power-tool
that referenced
this issue
Aug 23, 2022
strangeRabbit777
added a commit
to strangeRabbit777/high-power-tool
that referenced
this issue
Aug 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The documentation for
hx-push-url
starts withand this is both the expected behavior and semantically correct when the intended result of the operation is that after the htmx trigger completes, the contents of the current page will be diffed/swapped/manipulated to match the contents of the requested url, but without actually triggering a page load (e.g. purely progressive enhancement).
However, it seems that in reality it is the value of
hx-verb
that gets pushed to the history/navbar and not the url of the request, as demonstrated by the following:index.html:
contents.html:
This (correctly) triggers an XHR to
/contents.html?param1=foo
but the location pushed to the history API is/contents.html
rather than the true request URL.The text was updated successfully, but these errors were encountered: