Here's a sample of the markup where the trick lies in the nested hx-get within the hx-swap-oob marked element. Normally, without the extension the issue is that the oob-swap overwrites the initial hx-swap from the nested span. If I remove the hx-oob-swap it just works as expected and keeps adding the list items to the list, but of course the oob-swap doesn't work. This breaks a search form within the same page that assumes that the results will get oob-swapped. Maybe I should rethink how that works ? I like using oob-swap for form results since I can have multiple form controls (for example, desktop and mobile versions of filters, as completely separate markup), and it just magically works, until now lol