Preserves pre-disabled elements with hx-disabled-elt on other element #3443
+17
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Elements with
hx-disabled-elt
that were already disabled before sending request will now keep the disabled attribute after server has responded or timed out.A good chunk of the users are probably thinking that this doesn't matter because their html will always swap after request has completed but if they have set
htmx.config.timeout
the request can time out and elements that are supposed to be disabled will not be disabled anymore.The attribute
data-disabled-by-htmx
isn't set if the element already was disabled.Questions
Should I add a note to the documentation https://htmx.org/attributes/hx-disabled-elt/? Something like "Already disabled elements will not be affected"?
Corresponding issue: #3437
Testing
Test added:
preserve pre-disabled elements
.Checklist
master
for website changes,dev
forsource changes)
approved via an issue
npm run test
) and verified that it succeeded