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

No longer support Safari 13 #161

Closed
kid1412621 opened this issue Sep 20, 2019 · 9 comments
Closed

No longer support Safari 13 #161

kid1412621 opened this issue Sep 20, 2019 · 9 comments

Comments

@kid1412621
Copy link

kid1412621 commented Sep 20, 2019

Describe the issue

One or more specific URLs where the issue occurs

Screenshot in which the issue can be seen

Steps for anyone to reproduce the issue

Your settings

  • MacOS version: 10.14
  • Safari version: 13
  • uBlock Origin version: latest
Your filter lists
Your custom filters (if any)
@Bryzgalin
Copy link

Sad
gorhill@149b5cf

@ArtemBernatskyy
Copy link

Does this mean that uBlockOrigin will no longer support Safari ? Thx

@alvarnell
Copy link

Please see #158

@vassudanagunta
Copy link

There are good reasons why Apple changed how Safari works in a way that breaks uBlock Origin.

HackerNews has a good discussion of the pros and cons of Apple's philosophy: https://news.ycombinator.com/item?id=21025252

It's fair to disagree, and if you prefer the full control over the risk, your best option is Firefox. Chrome will soon also no longer support uBlock Origin.

@wuuuluojun
Copy link

Could you update when you are free?

@alvarnell
Copy link

@wuuuluojun, If you are referring to the developer, no, it's not going to be updated. You need to find an different solution.

@wuuuluojun
Copy link

@wuuuluojun, If you are referring to the developer, no, it's not going to be updated. You need to find an different solution.

What a pity , howeven many thanks.

@vdedyukhin
Copy link

Many still uses Safari 12, including me. I believe one last release will do no harm.

@RockyMM
Copy link

RockyMM commented Dec 21, 2019

Should be closed, as the explanation is given in #158

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

No branches or pull requests

8 participants