Open benbucksch opened 1 month ago
I don't make server calls if the UI doesn't ask for them. The OWA code is very similar to the IMAP code in that it unconditionally makes a server call every time the UI marks a message as read. I assume you're getting away with this in IMAP because the library requires you to lock the mailbox effectively serialising the requests?
I have no idea why your UI might be trying to grab focus. is it doing this in response to trying to display the error banner?
I assume the OWA calls that caused the server overload were not the markRead()
calls, but that this just happens to be the last one, and the server had already locked us out at this point. The OWA call that caused the overload was most likely another call.
FWIW, my paid (!) @outlook.com account was locked due to "terms of use violations" (maybe because of this bug, impossible to tell), so I cannot test anymore. This is a serious bug that might cause the user harm beyond Mustang, so we have to get this fixed.
Did you try the reproduction? Make sure to use a fresh @outlook.com account that you don't need.
I tried the reproduction with the Office 365 account but I didn't even hit my breakpoint on callOWA
once, so your STR are insufficient.
There are 2 problems here:
(Typo corrected)
Don't you mean our OWA client?
I did. Corrected.
Reproduction
Actual result
Expected result