Skip to content
Ellis Tsung edited this page Sep 6, 2017 · 3 revisions

Why do I have to re-enable/re-install the extension every time I restart Safari?

Make sure you are using the latest signed uBlock0.safariextz from here (all releases here are signed). Unsigned/self-signed builds will not persist across restarts, as an Apple Developer Certificate is required. All releases listed here have been signed with one.

Clicking Trust doesn't do anything when installing extension

If clicking Trust does not work, you may need to use keyboard controls:

  1. Launch System Preferences and open the Keyboard pane.
  2. Switch to the Shortcuts tab.
  3. Toggle All Controls to selected.
  4. Re-attempt to install the extension and use the Tab key on the keyboard to highlight Trust.
  5. Press the Space bar key to press the Trust button once selected.

Will there be support for the Content Blocker API?

Unlikely. JS Blocker on the topic:

Safari has a new feature called "Content Blockers" that allows for extremely efficient resource blocking on both the desktop and iOS version of Safari. As much as I'd like to incorporate this into JS Blocker, it is not feasible to do so. Using a content blocker will prevent JS Blocker from showing you exactly what's going on on a website (i.e. you won't see what's allowed or blocked.) It'll also break all of JS Blocker's "other" features, such as showing alerts within the webpage and canvas fingerprinting protection. Besides the loss of features, content blockers are limited to 50,000 rules. While this seems like a high number, it isn't enough for efficient protection and a lot of rules would need to be cut out to even run a content blocker. Until Apple eases the restrictions (or at least raises the number of rules that can be in a content blocker), JS Blocker will not be using this API.