#109690Prevent Chrome XMLHttpRequest deprecation messages
Description
Chrome reports in the Backend when Build/Sources/TypeScript/backend/storage/persistent.ts is used:
> Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.
WhatWG says:
> Synchronous XMLHttpRequest outside of workers is in the process of being removed from the web platform as it has detrimental effects to the end user’s experience. (This is a long process that takes many years.) Developers must not pass false for the async argument when the current global object is a Window object. User agents are strongly encouraged to warn about such usage in developer tools and may experiment with throwing an “InvalidAccessError” DOMException when it occurs.
The usage comes from the only Core place that sets `async=false`:
const request = new XMLHttpRequest();
const async = false;
request.open('GET', url.toString(), async);
request.send();
This means somehow™ we need to convert this in a working asynchronous call, ideally without breaking consumers
Reviews 1
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch
- Commit message
-
[TASK] Prevent Chrome XMLHttpRequest deprecation messages Resolves: #109690 Releases: main
History 23
-
Gerrit Code Review pushed patch set 1 for main to change 93803 status
NewUnder Review <span data-processor="relativetime" data-value="2026-04-22T18:46:38+00:00" > 04/22/26, 18:46 </span> -
Garvin Hicking commented and changed status
Under ReviewAccepted TYPO3 Version1415 <span data-processor="relativetime" data-value="2026-04-23T07:56:51+00:00" > 04/23/26, 07:56 </span> -
Georg Ringer changed Sprint Focus
On Location Sprint<span data-processor="relativetime" data-value="2026-08-06T15:50:22+00:00" > 08/06/26, 15:50 </span>
We’ll likely have to fully migrate to async, create a new module, deprecate the old one, have a breaking change for it too, ReST files yada yada