Over to jochen@, since they own the effort to deprecate sync XHR inside nested event loops. jochen@, what should we do here?

Thanks for reaching out. I guess you are aware of how to work around this issue, but I realize that changing a huge codebase on a short notice is difficult, so we will reconsider this change.

However, could you maybe share how you plan to act on the deprecation of sync XMLHttpRequests in general, so we can better plan how to proceed there?

Hi Jochen,
We have evaluated the work arounds - they woun't work for us. As we have multiple layers (technology, application, partner and customer extensions) all layers (including APIs) would be affected (a huge ammount of apps). The deprecation would mean for us to stop support of Chrome with our newest web technology.
Kind Regards, Andreas

Yes, I got that part. My question was, why is your newest web technology based on an API that's deprecated in all browsers? Ie right now, you should get two warnings: one about microtasks and one about sync xhrs in general. The latter is there since a long time - longer than promises are around.

Hi Jochen,
We are working on moving away from synchronous XHRs in the UI framework and we started to encourage application development teams in-house and our customers to adopt their applications step-wise. Our applications might be adopted within a dedicated period of time – but then also our customers would need to fix their applications. Our customers expect a high degree of stability and compatibility to run their enterprise applications.
Kind Regards, Andreas

glad to hear that you have plans to move away from sync XHRs, thank you!

I agree that a high degree of stability is desirable, however, that'll only work when we work together - not using deprecated APIs is part of that. Anyways, I removed this particular deprecation, so the feature will continue to work for now.

Thanks a lot, so far! Close cooperation is much appreciated!