We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://www.infinityfree.com/
Just like last time, the warning pop-up only appears on the InfinityFree website when using uBO.
Nothing.
uBlock Origin: 1.59.0 Chromium: 128 filterset (summary): network: 150498 cosmetic: 48230 scriptlet: 22277 html: 0 listset (total-discarded, last-updated): default: user-filters: 0-0, never ublock-filters: 39957-134, now ublock-badware: 11085-6, now ublock-privacy: 1126-2, now ublock-unbreak: 2471-1, now ublock-quick-fixes: 96-7, 1h.39m Δ easylist: 85924-573, now easyprivacy: 53049-781, now urlhaus-1: 25410-0, 1h.39m plowe-0: 3543-0, now filterset (user): [empty] trustedset: removed: chrome-extension-scheme moz-extension-scheme switchRuleset: removed: no-large-media: behind-the-scene false hostRuleset: removed: behind-the-scene * * noop behind-the-scene * image noop behind-the-scene * 3p noop behind-the-scene * inline-script noop behind-the-scene * 1p-script noop behind-the-scene * 3p-script noop behind-the-scene * 3p-frame noop userSettings: [none] hiddenSettings: [none] supportStats: allReadyAfter: 242 ms (selfie) maxAssetCacheWait: 19 ms cacheBackend: indexedDB
The text was updated successfully, but these errors were encountered:
I verified that this issue is not a duplicate. (Search here to find out.)
Continue in #25178
Sorry, something went wrong.
No branches or pull requests
Prerequisites
URL(s) where the issue occurs.
https://www.infinityfree.com/
Description
Just like last time, the warning pop-up only appears on the InfinityFree website when using uBO.
Other extensions used
Nothing.
Screenshot(s)
Screenshot(s)
Configuration
Details
The text was updated successfully, but these errors were encountered: