Bump target API to 33. https://redmine.stoutner.com/issues/902

[PrivacyBrowserAndroid.git] / app / src / main / assets / pt-rBR / guide_local_storage.html

diff --git a/app/src/main/assets/pt-rBR/guide_local_storage.html b/app/src/main/assets/pt-rBR/guide_local_storage.html
index 251bdad2f5fc9ea4cbffc275e7de80daff966051..2523f75a54bffbf73332028d815ed8c8de0eff23 100644 (file)
--- a/app/src/main/assets/pt-rBR/guide_local_storage.html
+++ b/app/src/main/assets/pt-rBR/guide_local_storage.html
@@ -45,6 +45,12 @@
         <p>Quase todos os sites com logins exigem que os cookies sejam ativados para o login do usuário.
             É assim que eles se certificam de que ainda é você conforme você passa de uma página para outra no site, e é, na minha opinião, o único uso legítimo para cookies.</p>
 
+        <p>Android's System WebView treats cookies as an app-level setting, meaning that cookies are either on or off for all tabs in Privacy Browser.
+            The result is that the cookies setting for whatever tab is currently displayed controls the cookies setting for all the background tabs as well.
+            If you have a tab in that background that has cookies enabled so that you can be logged into a website, and switch to a tab that doesn't have cookies enabled, it disabled cookies for all the tabs.
+            If the background tab makes a request, for example, to see if there is updated information, that request will be sent without cookies, which will cause the website to log you out.
+            This is a limitation that will be removed with the release of <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">Privacy WebView</a> in the 4.x series.</p>
+
         <p>Se os cookies estiverem habilitados, mas o JavaScript estiver desabilitado, o ícone de privacidade ficará amarelo <img class="inline" src="../shared_images/warning.svg"> como um aviso.</p>
 
 
@@ -52,10 +58,7 @@
 
         <p>Os cookies de terceiros são definidos por partes de um site que são carregadas de servidores diferentes do URL na barra de endereços.
             Não há um bom motivo para ativar cookies de terceiros. O Privacy Browser 3.8 removeu a opção e até o Google está planejando
-            <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">desativá-la no futuro</a>.
-            Nos dispositivos com Android KitKat (versão 4.4, API 19), WebView não
-            <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">diferencia entre cookies primários e de terceiros</a>.
-            Assim, habilitar cookies também habilitará cookies de terceiros.</p>
+            <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">desativá-la no futuro</a>.</p>
 
 
         <h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> Armazenamento DOM</h3>
@@ -74,5 +77,12 @@
             A partir do Android Oreo (versão 8.0, API 26), os dados do formulário WebView foram substituídos pelo
             <a href="https://medium.com/@bherbst/getting-androids-autofill-to-work-for-you-21435debea1">Autofill service</a>.
             Como tal, os controles para dados de formulário não aparecem mais em dispositivos Android mais recentes.</p>
+
+
+        <h3><svg class="header"><use href="../shared_images/delete_forever.svg#icon"/></svg> Clear and Exit</h3>
+
+        <p>Clear and Exit runs every time the last tab is closed or Clear and Exit is selected from the navigation menu.
+            By default it clears the cookies, DOM storage, form data, the logcat, and the WebView cache. Then it manually deletes the entire <code>app_webview</code> and <code>cache</code> directories.
+            The behavior of Clear and Exit can be configured in the settings.</p>
     </body>
 </html>
\ No newline at end of file