- Apr 25, 2013
Today we are releasing AdGuard for Safari 1.9.13. It has many fixes as you can see by the extensive changelog, but the most important ones would be the fixed memory leak, added dark theme for the element blocking window, fixed inverted allowlist behavior, and many general user interface improvements.
Speaking of design, see how beautiful and intuitive it looks now:
User rules are now available in the Filters section:
- [Added] Explanation of the permissions AdGuard for Safari uses #276
- [Added] "Export Logs" button in General settings #466
- [Added] Dark theme for "Block element on page" #476
- [Added] Autosave when importing rules #555
- [Enhancement] Modified UI behavior #402
- [Enhancement] The application icon is different from the extension icon #458
- [Enhancement] Moved the funnel and the green bar to the right side #463
- [Enhancement] Added a warning when selecting “Update interval - Do not update” #527
- [Enhancement] Content in the “General” and “Filters” sections moves upward when switching between them #529
- [Enhancement] Improved the export of inverted allowlist #544
- [Fixed] AdGuard isn't compatible with Web Annoyances Ultralist filter list #390
- [Fixed] $jsinject doesn't disable JS rules #484
- [Fixed] Update icon is cropped at the bottom #494
- [Fixed] Memory leak #505
- [Fixed] JS exceptions thrown on filter update/compilation (v1.9.3beta/v1.9.5beta on macOS 10.13.6) #525
- [Fixed] When Safari launches, the old AdGuard icon is loaded #528
- [Fixed] Pausing AdGuard doesn’t work properly #535
- [Fixed] Error when converting rules to Safari content blocking syntax #537
- [Fixed] “Allowlist” remains on when the slider is off #539
- [Fixed] The memory leak grows to 2GB, AdGuard for Safari doesn’t respond and crashes #542
- [Fixed] Format tag not replaced by the number of filters #566
- [Fixed] “Invert allowlist” behavior #568
- [Fixed] Small typos in source code files and formatting errors #403
- [Fixed] Checkbox in extension menu is not visible in dark theme #491
- [Fixed] The extension icon flickers while in pause mode when you refresh the page or switch tabs #497
- [Fixed] Wrong hyperlink color on the "About" page in dark theme #498
- [Fixed] Close the AdGuard Assistant window after clicking the “Report this website” #530
- [Fixed] Time changes when updating from the “Filters” section #538
- [Other] Improvements and UI fixes v.1.9.5 #543
- [Other] Minor fixes & improvements
- [Other] Localisation fix
We're back with an update of AdGuard for Safari. Though the last time we covered its release was quite a while ago, the product has been growing and developing all this time. Below you can find out what's new in the latest version.
You may have noticed that we had already released AdGuard for Safari. Sadly, we found a critical error that forced us to cancel v1.9.17. Now that we've fixed everything, we are re-releasing it feeling confident: the extension operates smoothly!
Apple silicon support
In November 2020, Apple began the switch from Intel processors to self-developed M1 chips. At the Apple Event, the manufacturer unveiled the new MacBooks with Apple silicon and the new M1 chip. But what is the fundamental difference between Intel and M1? We will try to explain it without getting too technical.
The brand new M1 processor is the first one in the family of ARM-based (Advanced RISC Machine) processors. M1 is a so-called system on a chip (SoC) that integrates components: USB controllers, Wi-Fi, Thunderbolt (interface), processor cores, video cards, and random-access memory (RAM). Unlike the old motherboard-based PC architecture, which separates components based on function, the new ARM аrchitecture brings them as close as possible. SoCs are great in terms of speed, as they allow to minimize latency for some functions: when elements are laid out in close proximity to each other, the interconnection delays can be minimized, while the data communication speed between modules, functional units, and memories is maximized.
We've been trying hard to make Macs with the new architecture compatible with the AdGuard extension for Safari, and are happy to introduce the result: a universal build that operates on both Intel and M1 processors.
Updated rules converter
We use rules converter only in two our products — AdGuard for iOS and AdGuard for Safari. It is required to convert AdGuard filtering rules into the ones of Safari, as their syntax differs from the commonly accepted one. In v1.9.17, we've added support for the $denyallow and $specifichide modifiers, cosmetic rules and Generic rules (exception rules modifiers), and fixed conversion errors.
Besides the converter, we've updated the app icon. And we couldn't do without fixing minor bugs, UI related and others.
Download AdGuard for Safari and share with us your thoughts on the new version. We'll be waiting for your feedback!
Being able to block ads and protect against trackers well sometimes takes a lot of work: this time we argued with Apple about the filtering rule limit — and succeeded! Now let us tell you how it was.
Why 50,000 is not enough
We once wrote that Apple had banned content blockers from using more than 50,000 filtering rules at a time. This was causing an obvious inconvenience. First of all, 50,000 is really not enough: our Base Filter now has about 30,000 rules. If you wanted to turn on another filter, the limit was exceeded. But this restriction can actually be circumvented: an application can use more than one content blocker. We took advantage of it by grouping the filters into 6 content blockers: General, Privacy, Social, Security, Other, and Custom. There are 50,000 rules in each of them — together it makes 300,000.
But even this division couldn't solve all the problems: users were getting notifications that the rules limit had been exceeded. During that, some rules from the filter didn't work and the filtering process failed.
Besides, some filters contain directives to transfer rules to another content blocker. If you had enabled multiple filters at once, some content blockers would get overrun too.
A small but important achievement
But we did actually succeed. We had written repeatedly to Apple on increasing the limit — and they kept saying no, arguing that the performance would degrade. But it seems that we’ve changed their minds: their tests were successful and the rule limit for each content blocker was increased to 150,000 — for our six content blockers, that’s 900,000 in total. This is three times more than before — which means that we’ll be able to apply the rules more flexibly, the filtering will become better, and users will have fewer chances to get into a situation where nothing works because the limit is exceeded.
What else we’ve changed
You might have noticed that our icon has been changed. Apple asked us to remove the Safari icon from our logo — and we appreciate that. But you definitely won’t get confused by our new one: it’s actually not that new.
Besides, we’ve updated the rules converter, scriptlets, and the Browser Assistant, and fixed some minor bugs. If you want to know more, there's always a full list of changes in our GitHub repository.
We hope you'll enjoy the new version of AdGuard for Safari. We're always happy to hear what you think of us — share your feedback in the blog comments, on social media, and on GitHub.
AdGuard for Safari 1.11.12Release date: March 23, 2023
AdGuard v1.11.12 for Safari offers a small, but important update for the extension’s better functioning and a better user experience. We’ve fixed a bug that’s been pestering us for some time: the extension’s settings window launched in full screen after OS startup. Plus, we have also updated Scriptlets and ExtendedCss.
AdGuard for Safari 1.11.15Release date: October 6, 2023
Some might say that not every release is worth celebrating, as they often consist of minor improvements and bug fixes. Well, we beg to differ. We are very proud to present to you the updated version of AdGuard for Safari. Our main focus here was to ensure compatibility with the new macOS Sonoma, which includes improving our extension overall.
To address this issue, we’ve merged two extensions into one, called AdGuard for Safari.
What else? We have successfully fixed the annoying issue of the settings panel opening on login. This problem had previously been resolved, but reappeared. Now everything is back to normal.
Finally, we have fixed several bugs in SafariConverterLib — the library responsible for converting AdGuard rules into a format supported by Safari. Our Scriptlets library, which contains short parameterized scripts used for advanced blocking rules, has also been updated. Now it’s your turn to update!
- Scriptlets updated to v1.9.72