Fell free to implement custom HttpBackend that uses Fetch API. For what I know, not all features can be implemented using fetch - there are issues with upload progress indication.

With the deprecation of IE11, there are no technical blockers to a fetch based backend that I'm aware of.

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

not all features can be implemented using fetch - there are issues with upload progress indication.

Well, there are issues with XHR as well, you can't get a readable stream for instances...
and what do you mean by all? the only thing i can really think of is progress event
fetch can be aborted using abortSignal

and progress can somewhat be monitored for progress if you can pipe the readable stream through a transform stream that calculates bytes that has passed through. but it is not the best solution as you need to know content-length and then it can not be compressed using gzip, deflate or br. It's not the best solution but something that kind of work in user land

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

The different design assumptions of fetch as compared to XHR means it's not a drop-in replacement with HTTPClient, and design changes would be needed. Until we do so, however, you can just use fetch on its own without HTTPClient, of course.

@dylhunn the main reason I switched from using fetch directly to using HTTPClient was that the latter is easy to stub out for testing, while the former would require that I start injecting a fetch alias with a token, then find or write a library for mocking requests during testing.

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

This issue will be used for future considerations for potential redesign of HttpClient.