From the “uBO works best in Firefox” page, I found this gem:
> Firefox will wait for uBO to be ready before sending network requests from already opened tab(s) at browser launch.
> In Chromium-based browsers, this is not the case. Tracker/advertisement payloads may find their way into already opened tabs before uBO is ready, while Firefox will properly filter these.
That’s a hell of a “bug” in Chromium, that blocker initialization has a race condition with restoring the last opened tabs. What a weird little “accident” that Chromium just moves forward and loads all the trackers, “oopsie”. I wonder which kind of promotion the engineer who made that “mistake” has been awarded.
> Firefox will wait for uBO to be ready before sending network requests from already opened tab(s) at browser launch.
> In Chromium-based browsers, this is not the case. Tracker/advertisement payloads may find their way into already opened tabs before uBO is ready, while Firefox will properly filter these.
That’s a hell of a “bug” in Chromium, that blocker initialization has a race condition with restoring the last opened tabs. What a weird little “accident” that Chromium just moves forward and loads all the trackers, “oopsie”. I wonder which kind of promotion the engineer who made that “mistake” has been awarded.