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

Adblock filter blocks manual browsing on pages that trigger the filter #427

Closed
Snuupy opened this issue Jun 26, 2018 · 0 comments
Closed
Labels
closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated.

Comments

@Snuupy
Copy link

Snuupy commented Jun 26, 2018

Description

Any website in an attempt to be loaded manually will not load if its URL triggers an adblock filter. It is not possible to disable adblock on that page, because it never gets loaded in the first place.

Steps to Reproduce

  1. Enter the URL of a website with a URL that will trigger the Brave filter list - ex. asdf.com/ad.html
  2. Hit [Enter]
  3. See that the URL bar has deleted the URL you wanted to browse to.

https://youtu.be/ApuO9Tvs8cs

Actual result:

URL bar goes from having a URL to no URL, with no feedback to the user. This confuses the user/dev.

Expected result:

Something like this: image

Reproduces how often:

always

Brave version (about:brave info)

Brave 67.0.3396.87

Reproducible on current release:

N/A, no current release

Website problems only:

  • Does the issue gets fixed with Brave Shields disabled?
    • Requires workaround to disable Brave Shields. Is not intuitive.
  • Does the issue reproduces on Chrome?
    • No, Brave Shields isn't on Chrome

Additional Information

Workaround: find a page (or create one) that links to the page you want to visit. Open that in a new tab, then disable brave shields on that page.

@bbondy bbondy added this to the Backlog milestone Jun 27, 2018
@rebron rebron modified the milestone: 1.x Backlog Feb 7, 2019
@bsclifton bsclifton added the closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. label Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated.
Projects
None yet
Development

No branches or pull requests

4 participants