1
0
mirror of https://github.com/gorhill/uBlock.git synced 2024-11-16 15:33:38 +01:00

Created page: "About Safari and Canary support"

garry-ut99 2024-07-14 17:45:35 +00:00
parent 06cef32588
commit c0e584dcef

@ -0,0 +1,33 @@
### Safari
There was support for Safari in the past, several years ago, but not anymore, and it's unknown whether will be again or not, however there are currrently ongoing active main discussions regarding it's revival in the coming future:
- [Explanation of the state of uBlock Origin (and other blockers) for Safari](https://github.com/el1t/uBlock-Safari/issues/158)
- [feature: maybe it's time to rethink the possibility of porting to Safari](https://github.com/uBlockOrigin/uBOL-home/issues/52)
- [Safari Version](https://github.com/gorhill/uBlock/issues/1596)
together with a big pile of unnecessary and redundant separate duplicate questions like this:
- [Is there going to be a Safari version coming soon?](https://github.com/uBlockOrigin/uBlock-issues/discussions/3197)
Hence there is no point in spamming the issue tracker by creating new separate duplicates over and over, discussion and sharing opinions should be continued in already existing main threads, new threads will be labeled as `invalid` or `duplicate` and closed.
### Canary
Chrome/Edge Canary are not officially supported, due to too high likelihood of breakage ([example](https://github.com/uBlockOrigin/uBlock-issues/issues/3217#issuecomment-2227376037)). Use either beta or stable.
Also there exists a big pile of invalid issues created over years by Canary users, many of them with an answer: "don't open issues with Canary":
- (01.2016) https://github.com/gorhill/uBlock/issues/1252#issuecomment-172654184
- (01.2016) https://github.com/gorhill/uBlock/issues/1253#issuecomment-172651477
- (02.2016) https://github.com/gorhill/uBlock/issues/1335#issuecomment-178927374
- (04.2017) https://github.com/gorhill/uBlock/issues/2546#issuecomment-294603426
- (08.2017) https://github.com/gorhill/uBlock/issues/2896#issuecomment-324897929
- (06.2018) https://github.com/uBlockOrigin/uBlock-issues/issues/57#issuecomment-394481405
- (08.2018) https://github.com/uBlockOrigin/uBlock-issues/issues/177#issuecomment-414500231
- (10.2018) https://github.com/uBlockOrigin/uBlock-issues/issues/273#issuecomment-430796056
- (11.2018) https://github.com/uBlockOrigin/uBlock-issues/issues/294#issuecomment-434950694
- (11.2018) https://github.com/uBlockOrigin/uBlock-issues/issues/294#issuecomment-435066706
- (04.2021) https://github.com/uBlockOrigin/uBlock-issues/issues/1562#issuecomment-824048891
- (06.2022) https://github.com/uBlockOrigin/uBlock-issues/issues/2139#issuecomment-1153992778
- (07.2024) https://github.com/uBlockOrigin/uBlock-issues/issues/3217#issuecomment-2227376037
Hence there is no point in spamming the issue tracker by creating new invalid issues over and over, new threads will be labeled as `invalid` or `duplicate` and closed.