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

Show filter list line number and go to filter line when link is clicked #620

Open
8 tasks done
sebast889 opened this issue Jun 5, 2019 · 5 comments
Open
8 tasks done
Labels
enhancement New feature or request

Comments

@sebast889
Copy link

Prerequisites

  • I verified that this is not a filter issue
  • This is not a support issue or a question
  • I performed a cursory search of the issue tracker to avoid opening a duplicate issue
    • Your issue may already be reported.
  • I tried to reproduce the issue when...
    • uBlock Origin is the only extension
    • uBlock Origin with default lists/settings
    • using a new, unmodified browser profile
  • I am running the latest version of uBlock Origin
  • I checked the documentation to understand that the issue I report is not a normal behavior

Description

It can sometimes be confusing to figure out which filters are causing blocks/allows from the logger and strict blocking page. Just an example ||domain.com^$~image and other similar negated filters and the new $all filters don't actually show up exactly in the logger and strict blocking pages.

It would better if the logger entry and strict blocking page show line number next to the filter list name and if the filter list link is clicked for it to automatically go to the line with the corresponding filter. This makes it easier to figure out what is the exact filter causing the blocks/allows.

@gwarser gwarser added the enhancement New feature or request label Jun 5, 2019
@uBlock-user
Copy link
Contributor

||domain.com^$~image

uBO interprets this rule as per the network request type, that's why it doesn't show up in the logger.

@sebast889
Copy link
Author

I know that. This request is to make it easier to find the actual written filter that is causing the block/allow, rather than what is finally interpreted by uBO.

@krystian3w

This comment has been minimized.

@gwarser

This comment has been minimized.

@garry-ut99

This comment was marked as abuse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants