Using Your Extension to Block Content

Your browser extension can use content-blocking rules to hide elements, block loads, and strip cookies from requests. Your extension provides the content-blocking rules in a structured format and WebKit compiles those rules into bytecode that it can process efficiently at runtime. As a result, Safari's page request will not include blocked content, such as third-party scripts. By avoiding unnecessary or unwanted downloads, Safari uses less memory and has better performance.

Earlier OS X content-blocking methodology used the onbeforeload event and canLoad message. Both those elements have been deprecated. If you provide a content-blocking rules file for your extension you can not access the onbeforeload event and canLoad message.

For more information on the Safari Content Blocking model, watch the WWDC 2015 session Safari Extensibility: Content Blocking and Shared Links. For information on how to format content-blocking rules, see Safari Content-Blocking Rules Reference.

Creating Content-Blocking Rules

Begin creating your content-blocking rules by examining the webpage resources with Safari Web Inspector. After identifying the elements you want to block, create content-blocking rules that match only those target elements and choose the actions to perform.

In Figure 12-1 the div element with the id "icon" has been selected in Web Inspector.

Figure 12-1  Selecting a page element

Figure 12-2 shows content blocking in action. The single rule in Listing 12-1 set the CSS for the "icon" element to display: none. Notice that the "icon" element is still in the HTML, but the element is not displayed.

Figure 12-2  After hiding an element

A set of content-blocking rules is represented as an array of rule dictionaries. Each rule dictionary contains a trigger and an action dictionary. The triggers tell Safari what circumstance activates the rule's action. The action tells Safari what to do with the selected web content, whether to block or not display the content or ignore previously listed rules. Listing 12-1 is a set of content-blocking rules containing one rule dictionary. The format for content-blocking rules is described in Safari Content-Blocking Rules Reference.

Listing 12-1  Hiding an element

    "trigger": {
        "url-filter": ""
    "action": {
        "selector": "#icon",
        "type": "css-display-none"

Adding Content-Blocking Rules to Your Extension

Now that you've created your content-blocking rules, you can compile them in a Safari extension. In Extension Builder click your extension’s icon to bring up the main interface, shown in Figure 12-3. Select the dropdown box "Content Blocker File" and choose your rules file.

Figure 12-3  Extension Builder's main interface

Dynamically Changing Content-Blocking Rules

You can provide your users customization options such as letting them choose what content to block and ignoring a block list when they are on a certain page. Save user input as a JSON string or a JSON object and call the JavaScript API method contentBlockingRules in your extensions's Global Page to dynamically configure your content-blocking rules. Listing 12-2 shows this method loading rules from an object named contentBlockingRules. Use the setContentBlocker method to clear the extension's previous settings by passing null or undefined.

Listing 12-2  Dynamically configuring content-blocking rules

var contentBlockingRules = [{
    "action": {
        "type": "block"
    "trigger": {
        "url-filter": ""