(01-24-2019, 06:13 AM)mikhoul Wrote: It's an issue I follow closely and sadly it seem more and more clear that Chrome will neuter the API.
Look at the official thread you can see that they just do service lips and that at the end they will change it almost exactly like in the draft.
https://groups.google.com/a/chromium.org...DiWfdrCwAJ
Official Issue: https://github.com/uBlockOrigin/uBlock-i...issues/338
What is you intention about it, will you keep the webRequest API as it is today ?
I really doubt that Chrome team will backtrack significantly.
I know that Brave seem to want to keep the "full webRequest API" if they need it but their adblocker is already integrated but nor as powerful like UBO or Nano Adblocker .
If you keep it compatible with with webRequest API that we have today you would make my day ;-) .
Regards
The problem is that most extensions are targeted at Chrome but not other Chromium browsers.
So even if these browsers keep webRequest API, it may make no big difference for these extensions.
Once Chrome takes that step, these extensions may change their design to fit Chrome, it is quite unlikely they will stick to webRequest API supported by other Chromium browsers.