Dashboard fails to display proper blocked counter
Kein opened this issue · 5 comments
I tried searching issues but could not find anything relevant for the common keywords I've used and I have no idea if a similar issue was submitted with some obscure keywords. Domain search also did not return any hits.
Prerequisites
- I performed a cursory search of the issue tracker to avoid opening a duplicate issue
- Your issue may already be reported.
- I also searched the existing issues at https://github.com/gorhill/uMatrix/issues
- This is not a support issue or a question
- Support issues and questions are handled at /r/uMatrix
- I tried to reproduce the issue when...
- uMatrix extension is wholly disabled or not installed
- uMatrix is the only extension
- uMatrix with default lists/settings
- using a new, unmodified browser profile
- I am running the latest version of uMatrix
- I checked the documentation to understand that the issue I report is not a normal behavior
- I used the logger to rule out that the issue is caused by my ruleset
Description
No dashboard counter data for requested resources.
A specific URL where the issue occurs
Steps to Reproduce
- Reset all to defaults, make sure web-workers on.
- Go to https://mail.yandex.ru
- Enable first-party scripts, if not enabled
- Reload and check dashboard - it does not indicate any
scriptrequests to https://yastatic.net - Check the logger and you can see there are requests made to https://yastatic.net/ which are blocked
Ruleset
All default.
Supporting evidence
Your environment
- uMatrix version: 1.4.1b0-devel
- Browser Name and version: Vivaldi 3.1/Chromium 83.0
- Operating System and version: windows7x64
I understand that the issue technically could be solved by taking a look at the logger and adding necessay rules, but as I understood, using basic logic and common sense, uMatrix dashboard was developed to be able to make rules on the fly and to avoid going through few thousands log lines per day.
I am unable to reproduce in Chromium 83/uMatrix 1.4.1b6.
Not sure what to say, I've managed to repro it just now in VM, clean Windows and clean Vivaldi 3.1 installation.
Haven't tried Chromium yet, will update.
Can you try with 1.4.1b6? Vivaldi is not officially supported. If it works in Chromium and not Vivaldi, then this needs to be reported to Vivaldi devs.
1.4.1b6 detected it first try even on Vivaldi (not gonna test Chromium then), my bad, should have used latest devel, Chrome store one was b0.
Chrome store one was b0
Yes, I realized that with your issue. I pushed b6 to the Chrome store yesterday -- currently pending review, this may takes long before it's cleared.