You can clone with
HTTPS or Subversion.
If a form has 2 sequential files, file1 and file2, I expect the "fileBegin" and "file" events to be fired in the order below (because it matches the payload content):
Instead, the events are fired in this order:
This is problematic because if I decide that file2 must be rejected (e.g. forbidden mime type), the connection destroyed, and all listeners removed from my form for cleanup, then it means I do not receive the "file" event for file1.
I do not have a fix yet, but I have made a test to demonstrate the issue in a commit in my fork:
The joys of async! This is the expect behavior at this point, but arguably not the most convenient. Feel free to propose a patch, but IMO you can use async control flow techniques to deal with it inside your app.