The order of execution of the event handlers should not matter. I cannot tell for sure but I think that the standard does not specify anything about that. Each implementation is free to choose whatever algorithm fits their flow best.
The event handlers should be independent. An event handler should not depend on another event handler or on the effects of the execution of another handler. An event handler should not even know that other handlers are installed for the same event.
If it does matter for you, then you have a coupling between the handlers. Either the coupling is artificial (for example, some data structure is shared, not because it needs to be shared but because that was the easiest way when the code has been written) and in this case you can remove it, or the coupling shows that the processing that should stay in one handler has been artificially split into two (or more) separate handlers.
Your question, in fact, reveals a problem in the architecture of the application. Solve the problem (make the event handlers independent) and, magically, you won't care any more in which order they are executed. Bonus, your application will be better designed and easier to modify and reason about its behaviour.