> The default queuing mode is bonkers

> By default, Htmx will cancel requests that are in-flight if you trigger another request on the same queue (element).

This seems like the only default that's reasonable to me

don't know if the author has a specific example in mind, but if a user submits an input, changes that input mid-request and submits again the request needs to be cancelled, otherwise the UI will be inconsistent by showing a response to an outdated input

Just processing one response after the other won't be possible if a response swaps out content with different IDs, so a second response won't be able to be swapped out in the same way