Skip to content
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

Logger is not logging every blocked element on reddit.com #2103

Closed
8 tasks done
JohnyP36 opened this issue May 4, 2022 · 2 comments
Closed
8 tasks done

Logger is not logging every blocked element on reddit.com #2103

JohnyP36 opened this issue May 4, 2022 · 2 comments
Labels
invalid not a uBlock issue

Comments

@JohnyP36
Copy link

JohnyP36 commented May 4, 2022

Prerequisites

I tried to reproduce the issue when...

  • uBO is the only extension
  • uBO with default lists/settings
  • using a new, unmodified browser profile

Description

See uBlockOrigin/uAssets#13072 (comment)

The point is: on reddit.com the logger doesn't log every blocked element

Screenshot

image

It only log the element from other domains (3p).
But if I turn on the DOM-inspector tada! you see there are elements blocked

Screenshot

image

A specific URL where the issue occurs

reddit.com

Steps to Reproduce

  1. Open the uBlock Logger
  2. Go to the homepage of reddit.com - just https://www.reddit.com/
  3. Scroll down the page for a while on reddit; don't click on posts; just scroll slowly down.
  4. Go back to the logger and notice that from the block element only ###ad-overlay from streamable.com is blocked.
  5. Switch in the logger to DOM-inspector
  6. See that multiple elements are blocked and not only the one stated in point 3.

Expected behavior

The Logger has to lock all blocked elements on the page.

Actual behavior

The Logger only logs blocked elements from an in the webpage inserted third party element,
but not the 1p elements.

uBlock Origin version

1.42.2

Browser name and version

MS Edge v101

Operating System and version

Windows 10, 21H2

@stephenhawk8054
Copy link
Member

Not sure if I understand correctly or not, but I can see the first party logs as normal.

Screenshot

image

@JohnyP36
Copy link
Author

JohnyP36 commented May 4, 2022

I double checked it. It seems there occurred an one time error, because now the Logger logs everything.

However, it's strange that this happens.

@gwarser gwarser added the invalid not a uBlock issue label May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid not a uBlock issue
Projects
None yet
Development

No branches or pull requests

3 participants