-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
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
uBO badge counter doesn't work when network requests originate from service-workers #1204
Comments
i just test with ABP and appears the numbers 🤔 |
was a cookies issue, after clean it.. works well |
well the solution has been short-duration.. again no numbers.. after 8-9 pages views |
It's a service worker making the requests, uBo considers that a different context |
Extension pages never show counter. Put the focus back on the webpage tab and the counter will appear. |
@llacb47 is right.
From what I gather, ABP will try to find from which page the requests originate -- it's a guest. As a result, if you open two or more pages to the site Given how service workers are becoming more common, I feel that something must be done about it, but ideally not with ABP's approach. |
Related issue: - uBlockOrigin/uBlock-issues#1204 Not much can be done beside reporting to tabless network requests to all tabs for which the context is a match. A short term local cache is used to avoid having to iterate through all existing tabs for each tabless network request just to find and report to the matching ones -- users reporting having a lot of opened tabs at once is not so uncommon.
Tested on Slack with |
in some websites the numbers of the "mini-icon" are not refreshed: but in other sites the numbers refresh when navigate in the site: |
URL(s) where the issue occurs
https://www.fotocasa.es/
Describe the issue
the uBO counter not working for me in this site. in the logs i can see blocked content.. but the counter in the uBO icon, no appears numbers.
no problem, in any other website.
Screenshot(s)
Versions
Settings
The text was updated successfully, but these errors were encountered: