Editing while request is in flight leads to lost events

1. Set up a form like this

<input hx-post="someURL" hx-trigger="keyup changed delay:1">

1. Set up a server that intentionally delays a few seconds before it responds.
2. Type “foo”
3. Observe the POST happening
4. Type “bar” while the server is delaying the response
5. Observe server response completing; even observe the UI acknowledge a successful save, if you have that wired up.
6. (Optional, for extra effect:) Walk to the kitchen and back
7. See everything on page looks successful, navigate away from the page
8. Notice that the server never saw “foobar”, only “foo”. You’ve lost data!

I think dirty state existing at a time when a request completes should submit another request immediately.

[1cg]

OK, I felt sufficiently bad about this to address it this morning. The fix is available in dev (and master, on accident).

[1cg]

No worries guy, yes, this is a very annoying issue if you are having things save on keystrokes, for example.

@mamcx intercooler is more mature and does the right thing, queuing up a request if another one is in flight, instead of cancelling it.

I plan on fixing this as soon as possible, but unfortunately some life events have made it very difficult to get open source work done.