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

Site-specific preferences get lost by navigating to different websites in the same tab + url list doesn't get cleared (uBlock Origin release 1.16.0) (Safari 11.1, OS High Sierra 10.13.4) #119

Open
ghost opened this Issue May 16, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@ghost
Copy link

ghost commented May 16, 2018

Describe the issue

There is an issue when you change the website and have site-specific preferences for the websites.
Also the url list doesn't get cleared.

One or more specific URLs where the issue occurs

For example: I startet at google.com and then navigated to facebook.com and then to github.com (All in the same tab)
When I start at Google, these are the settings (1):

(1)
bildschirmfoto 2018-05-16 um 17 56 48

When I navigate from Google to facebook.com, the urls of google are still in uBlock Origin (2). Also the facebook page does not work because my uBlock Origin preferences seems to be ignored (original preferences in picture (3))

(2)
bildschirmfoto 2018-05-16 um 17 57 03

(3)
bildschirmfoto 2018-05-16 um 17 57 51

Now, when I navigate from Facebook to GitHub.com, the urls from google (the first page) and Facebook (the second page) are still in the list of uBlock Origin. (4)

(4)
bildschirmfoto 2018-05-16 um 17 57 41

Steps for anyone to reproduce the issue

  1. Do this:
    Go to a website

  2. Then do this
    Go to an other website (same tab) with site-specific preferences

Your settings

  • MacOS version: 10.13.4
  • Safari version: 11.1
  • uBlock Origin version: 1.16.0
Your filter lists

Default filter lists + DE

@gkarag

This comment has been minimized.

Copy link

gkarag commented May 17, 2018

Looks like the same issue as #114

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment