As a part of out of renderer CORS support efforts, we will deprecate RegisterURLSchemeAsCORSEnabled interfaces soon.
The interface was removed half a year ago, but restored by Alexey because the interface was used by Electron (https://chromium-review.googlesource.com/c/chromium/src/+/768808).
Once we enable the network service, or browser side CORS support, we could not keep this interface as is. Since the Blink API does not have any promise to keep compatibility, we would just deprecate the interface.
See a design doc for "CORS support in Network Service", https://docs.google.com/document/d/1JNmUcvbw2UcjfdI2uyUpveHXCbae-DQ1n8d_sVs5fLg/edit?usp=sharing
Update:
Now I'm writing actual implementation to make it happen (though actual code path switch will happen later). Once we switch the code path by enabling the out-of-renderer CORS migration, the only way to do similar hack is to call url::AddCORSEnabledScheme() in the browser process. But it should not be per-renderer or per-frame, but global setting per-system (means maybe per electron app?).
Comment 1 by toyoshim@chromium.org
, Jan 10 2018