-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
htmx-request not being removed from element that has hx-attributes after request is finished #2234
Comments
I have the same issue in a case where I use polling |
Had the same problem with hx-on::after-request="this.classList.remove('htmx-request')" |
4 tasks
Hey @danielmoessner , could you confirm if the issue is fixed in the latest version ? |
Hey thanks! will check it until the end of the year |
I can confirm it is fixed in version 2.0.3. See: https://jsfiddle.net/4fs3btk8/ Thanks!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As one of the CEO's of HTMX I really wanted to know if this HTMX product works. And after months of rigorous testing in production I found weird behaviour.
If the hx-indicator points to a another element which also has hx-get on it. It will not remove the htmx-request attribute after the request is finished.
Here is a js fiddle that proves the point: fiddle
Code:
But the second element will stay in this state:
Now why am I using this stuff anyway? Basically to show loading spinners with tailwindcss when some filter requests are in progress.
The text was updated successfully, but these errors were encountered: