One more small Browser Assistant fix

This commit is contained in:
Vasily Bagirov 2020-08-17 14:05:57 +03:00 committed by GitHub
parent 12dc6ea0de
commit ba4729a23d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -33,9 +33,8 @@ When using the Browser Assistant, all these problems dont matter as there can
When AdGuard for Mac is installed for the first time, the thing a user encounters in the first place is the onboarding. During this process the user quickly learns about AdGuard's settings and can customize filtering to their liking. At one stage AdGuard will determine the user's default browser and provide them with a download link for the new Assistant.
<img src="https://cdn.adguard.com/public/Adguard/Release_notes/Mac/v2.4/assistant_onboarding_safari.png" style="border: 1px solid #efefef; max-width: 650px; padding: 2px;">
<p align="center"><i>An onboarding screen</i><p>
>On rare occasions, a browser may prove incompatible with the Browser Assistant, and the user will be offered to install the legacy version instead.
> On rare occasions, a browser may prove incompatible with the Browser Assistant, and the user will be offered to install the legacy version instead.
## Separate tab in settings
The new Browser Assistant has its own tab in AdGuard for Mac settings, together with Stealth Mode, Browsing Security, Parental Control and others. Dont worry if you missed the opportunity to install Browser Assistant during the onboarding, you'll find this option in the app's settings. Besides, there is a checkbox to enable the legacy Assistant.