uBlockOrigin / uMatrix-issues

This is the community-maintained issue tracker for uMatrix
https://github.com/gorhill/uMatrix
123 stars 17 forks source link

Dashboard fails to display proper blocked counter #276

Closed Kein closed 4 years ago

Kein commented 4 years ago

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

Description

No dashboard counter data for requested resources.

A specific URL where the issue occurs

https://mail.yandex.ru

Steps to Reproduce

  1. Reset all to defaults, make sure web-workers on.
  2. Go to https://mail.yandex.ru
  3. Enable first-party scripts, if not enabled
  4. Reload and check dashboard - it does not indicate any script requests to https://yastatic.net
  5. Check the logger and you can see there are requests made to https://yastatic.net/ which are blocked

Ruleset

All default.

Supporting evidence

image image

Your environment


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.

gorhill commented 4 years ago

I am unable to reproduce in Chromium 83/uMatrix 1.4.1b6.

Kein commented 4 years ago

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.

gorhill commented 4 years ago

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.

Kein commented 4 years ago

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.

gorhill commented 4 years ago

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.