Browser-extension Release - Versioni di AdGuard

Spring is bringing refreshing updates to AdGuard Browser Extension. We've made improvements to ExtendedCss and Scriptlets, and we're gearing up for something even bigger. Stay tuned for what's next.

È un aggiornamento tecnico volto ad aumentare la stabilità dell'app e a risolvere bug minori. Abbiamo anche aggiornati gli Scriptlets alla v1.7.13.

In questa versione abbiamo aggiornato il modulo Assistant, ExtendedCss e Scriptlets per bloccare ancora meglio gli annunci. Inoltre, abbiamo aggiunto a l'estensione gli scriptlets affidabili che offrano più funzionalità.

Questo aggiornamento include alcuni miglioramenti che rendono l'estensione più stabile.

Questo rilascio dell'estensione AdGuard Browser è minore, ma è altrettanto importante: con ogni aggiornamento, la nostra estensione migliora.

Questo piccolo aggiornamento non contiene cambiamenti maggiori per attirare l’attenzione. Qui abbiamo per lo più miglioramenti minori ed i scriptlet aggiornati.

Questa versione è un altro punto sulla tabella di marcia dell'estensione di browser AdGuard. Piccoli miglioramenti dell'interfaccia utente e alcune correzioni di bug, questo è tutto ciò che la versione offre. Ma si sa che ogni grande viaggio inizia (e continua) con piccoli passi.

Abbiamo appena lanciato l’Estensione di browser AdGuard v4.1.19 e abbiamo subito riscontrato un fastidioso bug: la quantità di regole del filtro veniva visualizzata in modo errato dopo l'aggiornamento dell'elenco dei filtri. Ecco quindi un aggiornamento che risolve questo problema e apporta alcuni miglioramenti generali.

È ora disponibile la nuova versione dell'estensione browser AdGuard v4.1.19. Installare l'aggiornamento: contiene diversi miglioramenti e correzioni di bug.

We always want to make the interface even more user-friendly for you and the filtering more efficient. That's exactly what the new version of AdGuard Browser extension has to offer.

We've made a lot of fixes and improvements: for instance, we added the Update filters button directly to the extension pop-up.

Quando si utilizza AdGuard, le buone notizie non tardano ad arrivare. Ecco la nuova versione dell'estensione AdGuard Browser. Questa versione è interamente dedicata alla correzione di bug, che migliorerà l'esperienza dell'utente.

Ad esempio, in precedenza alcuni scriptlet venivano visualizzati nella console degli Strumenti per sviluppatori anche quando il registro dei filtri era chiuso. Ora questo problema non esiste più.

Consulta il changelog completo per vedere le modifiche e poi aggiornare alla versione più recente!

Questa versione contiene alcune correzioni dei bug minori. Ma ognuno di loro ha migliorato l'estensione!

Come puoi vedere nel changelog, questo release non ha molto cambiamenti importanti: abbiamo semplicemente corretto alcuni bug IU ed UX. Tuttavia, ogni miglioramento è prezioso perché avvicina l'estensione AdGuard Browser all'ideale!

Questo è un aggiornamento minore che segue quello maggiore della v4.0.161. Probabilmente non noterete la differenza, ma va bene così: alcuni aggiornamenti passano inosservati.

In questa versione abbiamo risolto una vagonata di bug, elaborato il design della barra di scorrimento e aggiornato le traduzioni. Questo aggiornamento è piccolo ma efficiente.

[Aggiunto] color-scheme: dark; per i pagine post installatore e gli scrolls #1408 [Miglioramento] Scrollbar style #2010 [Corretto] Il carico della CPU aumenta al riavvio del browser con le schede aperte [Corretto] Il testo non entra nel pulsante #2024 [Corretto] La descrizione del filtro è troppo vicina al suo titolo e alle sue informazioni #2022 [Corretto] A volte le regole $replace non funzionano e non vengono visualizzate nel log del filtraggio #2018 [Corretto] Il cerchio intorno all'interruttore di protezione lampeggia quando si passa il cursore su di esso #2015 [Corretto] Errore di Firefox Nightly #2011 [Corretto] Phishing pop up e visibile su tutti i siti web #2009 [Corretto] Edge si offre di tradurre la pagina delle impostazioni in russo anche se è già in russo #2005 [Aggiornato] Traduzione cinese #2029

You’ve probably had this happen: you’re going to a party, everything seems perfect, and just before you leave you notice a stain on your clothes. What would you do? Change your look, of course. Well, we’ve noticed a little “stain” on the v4.0.133 release too: some users were unable to remove a domain from Allowlist after the update. And we’ve decided to release a new version right away with this bug fixed.

AdGuard Browser Extension 4.0 non è attualmente disponibile per tutti gli utenti. Il Chrome Store ha approvato una nuova versione della nostra estensione, ma è in corso un processo di rilascio graduale: la versione sarà distribuita gradualmente aumentando la percentuale di disponibilità per gli utenti. Altri negozi (Microsoft, Opera Addons, AMO) la stanno ancora esaminando. Se non vuoi aspettare che la nuova versione arrivi nello store, puoi scaricare la build su Github.

Presentazione dell'estensione per il browser AdGuard v4.0! Questo non è un semplice aggiornamento, ma una versione importante che offre un sacco di nuove funzionalità agli utenti dell'estensione.

Il refactoring è diventato una specie di parola d'ordine che implica una riscrittura enorme del codice, che abbiamo fatto per renderci la vita più difficile, ma più facile a lungo termine. Inoltre, abbiamo aggiunto il supporto per TSUrlFilter, la nostra nuova piattaforma di filtraggio che implementa le regole di blocco dei contenuti di AdGuard.

TSUrlFilter è un motore di filtraggio. Nelle applicazioni AdGuard, il suo posto è occupato dalle CoreLibs. TSUrlFilter è un modulo di applicazione delle regole che sarà utilizzato in vari progetti, tra cui AdGuard DNS.

Siamo passati al web design reattivo (o adattivo). Questo significa che gli elementi dell'interfaccia si adatteranno alle dimensioni dello schermo su entrambi i dispositivi desktop e mobili, indipendentemente dal modello.

Questo è conveniente sia per noi, dato che non abbiamo bisogno di sviluppare versioni separate dell'estensione del browser, sia per gli utenti - è sempre bello quando un'applicazione (o un'estensione del browser, in questo caso) è anche compatibile con l'interfaccia.

Ora il filtering log non solo è conforme ai principi del responsive web design, ma il suo aspetto generale è cambiato significativamente. Se hai usato il precedente registro di filtraggio, sarai in grado di notare la differenza: la nuova versione presenta la ricerca in schede, molti nuovi stati di richiesta e filtri che facilitano la ricerca delle richieste necessarie. I nuovi filtri e stati sono evidenziati, e i tooltip che spiegano ciascuno di essi appaiono quando si passa il cursore su di essi. A parte questo, è possibile visualizzare le richieste in anteprima e formattarle nella stessa finestra di dialogo - cliccando il pulsante "Beautify" rende più facile la lettura di queste richieste.

L'editor delle Regole utente può ora essere aperto in modalità a schermo intero, rendendo molto più conveniente aggiungere, modificare e cancellare le regole dei filtri. Infine, c'è una nuova azione sulla finestra popup di AdGuard Browser Extension che permette di reimpostare tutte le regole utente per il sito web attualmente aperto in una sola volta.

Inoltre, AdGuard Browser Extension ora presenta il tema scuro che tutti amano così tanto.

"Non ho capito ancora cosa rende TSUrlFilter migliore del precedente motore di filtraggio?", potrebbero chiedere i più curiosi. Probabilmente il vantaggio principale sono i nuovi modificatori: $removeheader, $redirect-rule, $ping, $path, $noop e $denyallow. E il modificatore $redirect è stato notevolmente migliorato, così che ora tutte le regole $redirect su un sito web possono essere sovrascritte applicando @@||example.org^$redirect.

In this version we've fixed only one, but nevertheless important issue.

We considered the latest update to be the last before the big 4.0 release. Well, we were wrong. Here is the last one (hopefully): some minor changes and scriptlets updates. Soon you all will become witness to something really epic!

This is the last update before the big 4.0 release coming this November. Wait a bit more and you’ll see how many changes it brings.

Psst, here is a BTS promo in the latest version of the AdGuard Browser Extension. Get yours updated! Don’t get overexcited though, BTS here stands for “back to school” and not what you thought, but it’s still cool, right?

This release is a hotfix for an issue that came up with the previous release.

[Fixed] $removeparam modifier must not remove search params from POST requests #1812

AdGuard Browser Extension v3.6.5 is released.

We’ve added support for the $removeparam modifier which allowed us to get rid of the old Remove tracking parameters setting and add a new one that enables AdGuard URL Tracking filter. This will make deleting tracking parameters more flexible, so that everybody can create $removeparam user rules for their needs.

Moreover, in addition to “Do-Not-Track”, another signal appeared in the Stealth Mode settings — “Global Privacy Control”. These signals are sent to the websites you are visiting not to track you and to hide your search queries. Finally, we’ve added the birthday promo to the extension — AdGuard turns 12 on June 1!

Another small but important… Oh please, spare me this. The extension looks a bit brighter now that we have an Easter promo. And of course, the new version includes a basic starter pack of each release, big or small: we’ve updated filters, extended CSS to v1.3.10, scriptlets — to v1.3.15, and AdGuard Assistant — to v4.3.45. These are small preparatory steps for the coming update. Trust us, it’s going to be epic.

A small but important release. We’ve added a new pseudo-class :is() and upgraded extended CSS to v1.3.8. :is() is a CSS pseudo-class function that comes in handy for writing large selector lists more compactly. Now AdGuard AdBlocker extension supports this functionality.

Another brick in the wall: building our perfect browser extension. It seems that the few latest updates passed without notice – it’s no wonder ’cause we didn’t show to users any visible change. Yet, don’t let yourself be disappointed with the same old mantra: Scriptlets, Extended-CSS, and filters. They matter. So, we’ve updated Scriptlets to v1.3.13 and Extended-CSS to v1.3.6. AdGuard Assistant has been updated to v4.3.37. Plus, we’ve added new translations and filters to this version.

When you're on a journey to the perfect ad blocker, every step matters. Even if it's on the smaller size like today: in this update, we only touched on scriptlets and extended CSS optimization.

The new version of AdGuard AdBlocker extension has been released. We’ve updated the scriptlets, locales, and extended CSS — and that’s just the tip of the iceberg. This beta harbours many secrets: many changes remained under the hood, but rest assured, they will improve the app’s performance.

The release of AdGuard AdBlocker extension v3.5.12 was preceded by four betas the version numbers of which look like Fibonacci sequence: 3.5.3, 3.5.5, 3.5.8 (and 3.5.12 falling out of line)… Seems like we’re getting close to the golden ratio! We hope that you’ll find the changes we made to the extension beautiful and well calibrated.

In this small hotfix we update scriptlets and related metadata.

This is a small update that fixes a few ad blocking- and networking-related bugs, as well as introduces some other minor improvements in UI and other areas.

Fixed an issue with AdGuard add-on running upgrade script even when the add-on was not actually updated.

A small update to enter the new year with a little bit less bugs :)

Today’s update is something in-between a hotfix and a regular release. It lacks in numbers of changes compared to some other versions, but isn’t a hotfix either as we don’t patch any specific bug. All in all, consider it a quality of life update.

Your average grocery list is probably longer than this update’s changelog, but don’t let it fool you. We introduce two powerful new tools that are going to serve well to filtering rules creators and will noticeably improve the ad blocking quality.

Scriptlets is a powerful ad blocking instrument. You can say that scriptlet is an internal script (a mini-program) that we install in the extension, and then execute that script with the help of filtering rules. Putting it simply, scriptlets allow us to modify how the code of the web page behaves. As for the practical use, this helps to block anti-ad blockers, for example.

They are practically the same modifiers, and they allow to substitute resources. If you are not a custom filtering rules aficionado, don't bother with it. Just know that it is yet another instrument in the hands of filter developers that helps efficiently block ads.

We should mention that both $redirect and $rewrite modifiers are still kind of working in test mode, but they are fully operational and you should feel free to use them.

After a series of hasty hotfixes we are happy to finally do a full-scale release. It may be not the biggest AdGuard browser extension release of all times, but it’s something. Inside you will find some small-ish changes and of course more bug fixes! This time, they were not so urgent, though.

Sorry for another hotfix. It appeared, that filter lists updates were broken since v3.0 first release for those who restart their browser too often. This update fixes #1346and #1331.

Turned out, we overlooked a couple of minor bugs and inconsistencies in the previous hotfix. Here's a quick fix to set things right.

[Fixed] Statistics flushed after browser restart (randomly) #1341
[Fixed] ExtCss DOM observer fails in Edge due to a "Syntax error" #1330
[Fixed] Extension doesn't search for other rules if first found rule matched with badfilter rule #1328
[Fixed] User filter editor is often stuck in "Saving" state #1316
[Fixed] AdGuard extension does not properly show on Chrome 56 (winXP) #1315
[Fixed] AdGuard extension doesn't work in UC browser #1318
[Fixed] ExtendedCss recursively calls MutationObserver #1317

As they say, you can't have a good release without a hotfix. Or maybe they don't say that, but we sure need one.

In this update, we fix a particularly nasty bug that causes high CPU load because of some filtering rules.

New AdGuard Browser Extension follows the trends. As if ads were not bad enough, the web today is teeming with trackers. Big companies want to know everything about you, and AdGuard is here to stop it. The new Stealth Mode is designed specifically to protect your online privacy — an entire new module dedicated just for that. But that’s even not the first thing you will notice. Of course, the new design will steal the show. Let’s have a closer look.

Fresh icon and menu designs that make interface more natural and user-friendly, with a big ‘On/Off‘ switch. Brand-new ’Statistics" tab creates charts based on your blocked ads statistics, with the ability to show different types of data: total, filter-specific etc.

Also worth mentioning is the User filter. It has undergone a few changes too. The new luminous element highlighting and auto-save function, as well as a unified text field for filtering rules should make editing more convenient. The text box can also be resized to your liking.

We took online privacy protection in our extension to the next level by adding the Privacy module, which until this day existed only in the standalone AdGuard for Windows app. Although it doesn’t have the full capabilities of its desktop parent yet, it still makes the extension all the more effective for protecting privacy against trackers and analytical systems. It already gives you a wide range of privacy-related options (each explained in the tooltip), but we will surely add more in the future updates.

We changed the way in which the filters are presented to users. Instead of listing them all together, we combined the filters into semantic groups. Each group includes filters that serve some particular goal. For example, filters that block ads are grouped together, filters that block trackers and serve privacy purposes will be united into a different group, etc. It is possible to enable and disable all filters in a group at once.

Before, filters were automatically updated every 48 hours (default period), now you can adjust the frequency of automatic updates (by choosing from options: every 1/6/12/24/48 hours) or disable them completely, in case you prefer to update them manually.

If you already have the AdGuard app, our browser extension may become a very useful additional tool, which can completely replace the browser-based ’AdGuard Assistant" module (learn more). It’s called Integration mode and now you can turn it on or off in the ‘Other settings’ tab.

Among important changes is a fix to the Assistant "block" button issue and a new "Save filtering log" feature that will come handy for filter developers and in some cases of troubleshooting via support.

This update adds several minor-ish (although filter enthusiasts will argue) features to the Filtering Log and improves ad blocking quality. You'll find an array of bug fixes, as usual.

Applied element hiding rules are now highlighted with yellow color in the Filtering Log. This will greatly help parse log entries. We don't need to prove it to you if you are actively using it :)

Again, another treat for filtering rules creators. Previously you had to list domains old-fashioned way: example.com,example.eu etc, and now you can simply use example.* syntax.

To efficiently block ads on the page we need a way to reliably inject our scripts before the in-page scripts are executed. A set of measures has been taken to ensure this. While there is still no 100% guarantee, the success chance has increased considerably — along with ad blocking quality.

Ho Ho Ho! Just kidding, it is not Christmas, but it might have very well been — isn’t every AdGuard Browser Extension release a special day for you? For us, it certainly is 🙂 This time we prepared a couple or two of quite important changes and improvements, to come along with a long list of more routine-ish fixes. Read on to find out the details.

For a while now we develop AdGuard Assistant more or less independently, to later use it wherever we need — Windows and Mac apps use regular Assistant, Android and iOS apps use mobile version. Browser extension users encounter Assistant when they click "Block ads on this website" button. We will not go into the details here, those who interested can find the exhaustive changelog inside the Assistant repo.

There was a certain change in Chrome browser recently, that prompted us to respond by reconsidering the way we inject scripts and styles. The good thing is, thanks to this change we now have less bugs, more possibilities and were even able to make the extension more lightweight by reducing the amount of code.

This change is on the technical side, but from the end user perspective it converts into better performance and better quality ad blocking, thanks to more tools being available to the extension now.

Ad blocking has been enhanced in this version by adding support for several modifiers. We've also integrated the extension with our web reporting tool, details below. As usual, all spotted bugs have been fixed too, this mostly concerns Firefox version.

A new convenient way to report any issues with websites, be it missed ads, false positives, unblocked social widgets etc. Just head to the problematic website, bring up the context menu and select "Submit a complaint" option. You will be transferred to reports.adguard.com and a wizard will take you through the required steps to report the issue — and most of the fields will be even filled out automatically. Try it!

A long time has passed since the last release. But we weren't sitting on our hands. We fixed a whole lot of various bugs, so most users will find something positive in this update. This version also contains some sweet additions that will be interesting mostly for rule creators.

This one is a rather obvious: when you use the manual blocking tool to create a rule, you can now give this rule a higher priority by ticking the checkbox. The $important modifier was available before, but you had to manually add it via the user filter.

[Added] $csp modifier support: #685

This is strictly for the rule creators, as it requires the basic understanding of the Content Security Policy security layer.

This modifier completely changes the rule behaviour. If it is applied to a rule, it will not block the matching request. The response headers are going to be modified instead.

You can find the syntax and examples for csp inside the issue.

We had been waiting for this for a long time, it took a lot of time but now the code is much more simple and convenient to work with.

The builds themselves are now available directly on GitHub, all the updates will be stored here. The build names are now more clear and understandable.

There are few notable changes in this release that take place in Firefox version. First of all, FF have finally released the WebExtensions technology which allowed us to completely revamp the extension code. It now greatly resembles the code for Chrome extension, which makes it much easier for further development among other advantages. A lot of other improvements have been done, too.