fix stale hx-* handlers on re-process#3835
Open
scriptogre wants to merge 1 commit into
Open
Conversation
Mutating hx-trigger, hx-on, or hx-boost on an initialized element now takes effect.
26b48df to
35044f5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes stale hx-on/hx-trigger handlers after morph or re-process.
Previously:
Now only the current handler fires. Cleanup is scoped to elements whose wiring attrs (hx-trigger, hx-boost, hx-on*) actually changed.
hx-valschanges,hx-triggerwithoncemodifiers, and child elements are unaffected.Adds 12 tests. All of #3830 / #3834's tests pass.
Related: #3830, #3834