Yes, we should remove this, as well as the password-credential codepath from the loader all the way up the stack.
battre@: Do you have a feel for a reasonable timeline here? We originally said M62, which the deprecation messages still point to (we're on M64 now). I'd like to get rid of this code, as it complicates the network stack migrations that are ongoing. :)
> Before I start working on a CL, can you quickly confirm that the goal is to
> basically delete all code added here
> https://bugs.chromium.org/p/chromium/issues/detail?id=599597? I.e. that the
> goal is not to introduce any kinds of warnings.
Correct. We deprecated this API months ago, we said we were going to remove it in M62. We missed that deadline. *shrug* Now seems like a great time to get rid of the code.
Bumping the priority a bit, as this is making the loading team's job a little harder than it should be while they're refactoring things like CORS. It would be lovely to reduce the complexity of the loading stack by removing this code we don't want to support anymore. :)
Comment 1 by toyoshim@chromium.org
, Oct 26 2017