fix: improve HTMX processing for attacks tab by targeting all containers#163
Merged
BlessedRebuS merged 1 commit intodevfrom Apr 2, 2026
Merged
fix: improve HTMX processing for attacks tab by targeting all containers#163BlessedRebuS merged 1 commit intodevfrom
BlessedRebuS merged 1 commit intodevfrom
Conversation
BlessedRebuS
approved these changes
Apr 2, 2026
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
2 participants
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.
This pull request updates the way HTMX containers are processed in the attacks tab of the dashboard. Instead of processing only a single newly inserted element, the code now processes all relevant HTMX containers within the
.alert-section, ensuring that dynamic content is properly initialized.Improvements to HTMX processing in the attacks tab:
.htmx-container[hx-get]elements within.alert-sectioninstead of just the next sibling of a specific template, ensuring more robust initialization for dynamically loaded content.