I think it's time for Microsoft to rethink their decision to base Edge on Chromium.
It's a painful decision, to be sure, but the Microsoft team has to make a decision here: fork or adhere. The immediate benefit of forking and not following Chromium on this change is obvious. However, the cost of the fork will grow over time and it will be in Google's interest to deprecate and replace all of the infrastructure that supports the webRequest API to make it maximally painful to maintain the functionality in a fork.
On the other hand, had Microsoft decided to base Edge on Gecko, they wouldn't be working off a forked codebase whose owner has a perverse incentive to make the fork as painful and expensive as possible.
How many engineer hours, months, years are going to be wasted just shoring up features like this?
It's a painful decision, to be sure, but the Microsoft team has to make a decision here: fork or adhere. The immediate benefit of forking and not following Chromium on this change is obvious. However, the cost of the fork will grow over time and it will be in Google's interest to deprecate and replace all of the infrastructure that supports the webRequest API to make it maximally painful to maintain the functionality in a fork.
On the other hand, had Microsoft decided to base Edge on Gecko, they wouldn't be working off a forked codebase whose owner has a perverse incentive to make the fork as painful and expensive as possible.
How many engineer hours, months, years are going to be wasted just shoring up features like this?