Durch die Nutzung von Cookies stellen diese Internet-Seiten sicher, daß es sich um denselben angemeldeten Benutzer handelt, der von Seite zu Seite innerhalb einer Website navigiert.
Dies ist vermutlich die einzige legitime Nutzung von 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>Wenn Cookies aktiviert sind, aber JavaScript deaktiviert ist, wird das Privatsphären-Icon <img class="inline" src="../shared_images/warning.svg"> zur Warnung in gelb dargestellt.</p>
<h3><svg class="header"><use href="../shared_images/cookie.svg#icon"/></svg> Drittanbieter-Cookies</h3>
<p>Drittanbieter-Cookies werden von Teilen von Websites gesetzt, die von anderen Servern geladen werden als von dem, dessen Adresse (URL) in der Adresszeile des Browsers angezeigt wird.
Es gibt eigentlich keinen guten Grund, solche Cookies überhaupt zuzulassen. Ab Privacy Browser Version 3.8 wurde die Option daher entfernt und selbst Google plant,
- <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">Drittanbieter-Cookies in Zukunft zu deaktivieren</a>.
- Auf Geräten mit Android KitKat (Version 4.4, API 19), unterscheidet WebView nicht
- <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">zwischen Erstanbieter- und Drittanbieter-Cookies</a>.
- Daher werden bei solchen Geräten immer auch Drittanbieter-Cookies zugelassen, sobald Cookies aktiviert sind.</p>
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">Drittanbieter-Cookies in Zukunft zu deaktivieren</a>.</p>
<h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> DOM-Speicher</h3>
<p>Privacy Browser nutzt Android's eingebaute WebView-Komponente zum Anzeigen von Websites.
Daher gibt es einige Einschränkungen in Bezug auf die von WebView bereitgestellten Kontrollmöglichkeiten der Privatsphäre-Einstellungen.
Zum Beispiel ist es nicht möglich, manche JavaScript-Kommandos zu aktivieren und andere zu deaktivieren.
- Für die Zukunft ist geplant, dass Privacy Browser zu einer eigenen WebView-Komponente namens <a href="https://www.stoutner.com/category/roadmap/">Privacy WebView</a> wechselt.</p>
+ Für die Zukunft ist geplant, dass Privacy Browser zu einer eigenen WebView-Komponente namens
+ <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">Privacy WebView</a> wechselt.</p>
</body>
</html>
\ No newline at end of file
<p>Almost all websites with logins require cookies to be enabled for a user to log in.
That is how they make sure it is still you as you move from page to page on the site, and is, in my opinion, the only legitimate use for 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>If cookies are enabled but JavaScript is disabled, the privacy icon will be yellow <img class="inline" src="../shared_images/warning.svg"> as a warning.</p>
<p>Third-party cookies are set by portions of a website that are loaded from servers different from the URL at the top of the page.
There is no good reason to ever enable third-party cookies. Privacy Browser 3.8 removed the option, and even Google is planning to
- <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">disable them in the future</a>.
- On devices with Android KitKat (version 4.4, API 19), WebView does not
- <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">differentiate
- between first-party and third-party cookies</a>. Thus, enabling cookies will also enable third-party cookies.</p>
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">disable them in the future</a>.</p>
<h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> DOM Storage</h3>
<h3><svg class="header"><use href="../shared_images/subtitles.svg#icon"/></svg> Form Data</h3>
- <p>Form data contains information typed into web forms, like user names, addresses, phone numbers, etc., and lists them in a drop-down box on future visits.
+ <p>Form data contains information typed into web forms, like usernames, addresses, phone numbers, etc., and lists them in a drop-down box on future visits.
Unlike the other forms of local storage, form data is not sent to the web server without specific user interaction. Beginning in Android Oreo (version 8.0, API 26),
WebView’s form data was replaced by the <a href="https://medium.com/@bherbst/getting-androids-autofill-to-work-for-you-21435debea1">Autofill service</a>.
As such, controls for form data no longer appear on newer Android devices.</p>
<p>Privacy Browser uses Android’s built-in WebView to render websites. There are some limitations in the controls WebView exposes for managing privacy settings.
For example, it isn’t possible to enable some JavaScript commands while disabling others.
- In the future, Privacy Browser will switch to a custom WebView called <a href="https://www.stoutner.com/category/roadmap/">Privacy WebView</a>.</p>
+ In the future, Privacy Browser will switch to a custom WebView called <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">Privacy WebView</a>.</p>
</body>
</html>
\ No newline at end of file
<p>Casi todas las páginas web con logins requieren que las cookies estén habilitadas para que el usuario pueda iniciar sesión.
Así es como se aseguran de que sigues siendo tú al pasar de una página a otra de la web, y es, en mi opinión, el único uso legítimo de las 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>Si las cookies están activadas pero JavaScript está desactivado, el icono de privacidad será amarillo <img class="inline" src="../shared_images/warning.svg"> como advertencia.</p>
<p>Las cookies de terceros son instaladas por partes de un sitio web que se cargan desde servidores diferentes a la URL que aparece en la parte superior de la página.
No hay ninguna buena razón para activar las cookies de terceros. La versión 3.8 de Privacy Browser eliminó la opción, e incluso Google planea
- <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">desactivarlas en un futuro.</a>.
- En dispositivos con Android KitKat (versión 4.4, API 19), WebView no
- <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">distingue entre cookies de origen y de terceros</a>.
- Por lo tanto, si se habilitan las cookies, también se habilitarán las de terceros.</p>
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">desactivarlas en un futuro.</a>.</p>
<h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> Almacenamiento DOM</h3>
<p>Navegador Privado usa el WebView que incorpora Android para interpretar los sitios web.
Existen algunas limitaciones en los controles que WebView expone para administrar la configuración de privacidad.
Por ejemplo, no es posible habilitar algunos comandos JavaScript mientras que se deshabilitan otros.
- En el futuro, Navegador Privado cambiará a un WebView personalizado llamado <a href="https://www.stoutner.com/category/roadmap/">WebView Privado</a>.</p>
+ En el futuro, Navegador Privado cambiará a un WebView personalizado llamado <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">WebView Privado</a>.</p>
</body>
</html>
\ No newline at end of file
<p>La quasi-totalité des sites web avec des identifiants nécessitent que les cookies soient activés pour qu'un utilisateur puisse se connecter.
C'est ainsi qu'ils s'assurent qu'il s'agit toujours de vous lorsque vous passez d'une page à l'autre du site, et c'est, à mon avis, la seule utilisation légitime des 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>Si les cookies sont activés mais que JavaScript est désactivé, l'icône de confidentialité sera jaune <img class="inline" src="../shared_images/warning.svg"> en guise d'avertissement.</p>
<p>Les cookies tiers sont définis par les parties d'un site web qui sont chargées à partir de serveurs différents de l'URL en haut de la page.
Il n'y a aucune bonne raison d'activer les cookies tiers. Privacy Browser 3.8 a supprimé cette option, et même Google prévoit de
- <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">les désactiver à l'avenir</a>.
- Sur les appareils équipés d'Android KitKat (version 4.4, API 19), WebView n'est pas
- <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">différencié
- entre les cookies internes et les cookies tiers</a>. Par conséquent, l'activation des cookies activera également les cookies tiers.</p>
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">les désactiver à l'avenir</a>.</p>
<h3> <svg class="header"><use href="../shared_images/web.svg#icon"/></svg> Stockage du DOM</h3>
<p>Privacy Browser utilise WebView intégré à Android pour afficher les sites Web. Il existe certaines limitations dans les contrôles que WebView applique pour gérer les paramètres de confidentialité.
Par exemple, il n'est pas possible d'activer certaines commandes JavaScript tout en en désactivant d'autres.
- À l'avenir, Privacy Browser basculera vers une vue Web personnalisée appelée <a href="https://www.stoutner.com/category/roadmap/">Privacy WebView</a>.</p>
+ À l'avenir, Privacy Browser basculera vers une vue Web personnalisée appelée <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">Privacy WebView</a>.</p>
</body>
</html>
\ No newline at end of file
<p>Quasi tutti i siti web con login richiedono che i cookies siano abilitati perché l'utente possa accedere.
E' questo il metodo che utilizzano per essere sicuri che sia sempre lo stesso utente che si sposta da una pagina all'altra del sito ed è, a nostro parere, l'unico utilizzo legittimo dei 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 i cookies sono abilitati ma JavaScript è disabilitato, l'icona della privacy sarà gialla <img class="inline" src="../shared_images/warning.svg"> come avvertimento.</p>
<p>I cookies di terze parti sono impostati da porzioni di un sito web che sono caricate da server diversi dalla URL in cima alla pagina web.
Non esiste mai alcuna ragione valida per abilitare i cookies di terze parti. Privacy Browser 3.8 ha rimosso questa opzione, e anche Google sta pianificando di
- <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">disabilitarli in futuro</a>.
- Sui dispositivi con Android KitKat (versione 4.4, API 19), WebView non
- <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">fa distinzione
- tra i cookies proprietari e i cookies di terze parti</a>. In questo modo abilitare i cookies significa abilitare anche quelli di terze parti.</p>
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">disabilitarli in futuro</a>.</p>
<h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> DOM Storage</h3>
<p>Privacy Browser utilizza il WebView nativo di Android per la visualizzazione dei siti web.
Esistono alcune limitazioni nei controlli disponibili di WebView per la gestione delle impostazioni della privacy.
Ad esempio non è possibile abilitare alcuni comandi JavaScript disabilitandone altri.
- In futuro Privacy Browser sarà dotato di una WebView personalizzata denominata <a href="https://www.stoutner.com/category/roadmap/">Privacy WebView</a>.</p>
+ In futuro Privacy Browser sarà dotato di una WebView personalizzata denominata <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">Privacy WebView</a>.</p>
</body>
</html>
\ No newline at end of file
<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>
<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>
<p>O Privacy Browser usa o WebView integrado do Android para renderizar sites. Existem algumas limitações nos controles que o WebView expõe para gerenciar as configurações de privacidade.
Por exemplo, não é possível habilitar alguns comandos JavaScript enquanto outros desabilitam.
- No futuro, o Privacy Browser mudará para um WebView personalizado chamado <a href="https://www.stoutner.com/category/roadmap/">Privacy WebView</a>.</p>
+ No futuro, o Privacy Browser mudará para um WebView personalizado chamado <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">Privacy WebView</a>.</p>
</body>
</html>
\ No newline at end of file
<p>Почти все сайты с логинами требуют, чтобы для авторизации пользователя были включены cookie.
Именно так они удостоверяются, что это все еще вы, когда переходите со страницы на страницу на сайте, и, на мой взгляд, это единственное законное использование файлов cookie.</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>Если cookie включены и при этом JavaScript отключен, то значок конфиденциальности будет желтого цвета <img class="inline" src="../shared_images/warning.svg"> в качестве предупреждения.</p>
<p>Сторонние файлы cookie устанавливаются фрагментами сайта, которые загружаются с серверов, отличных от указанного в адресной строке.
Не существует никаких веских причин для включения сторонних файлов cookie. В Privacy Browser 3.8 эта опция была удалена, и даже Google
- <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">планирует отключить ее в будущем</a>.
- На устройствах под управлением Android KitKat (версия 4.4, API 19) WebView
- <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">не различает
- первичные и сторонние файлы cookie</a>. Таким образом, включение файлов cookie приводит и ко включению сторонних cookie.</p>
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">планирует отключить ее в будущем</a>.</p>
<h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> DOM-хранилище</h3>
<p>Privacy Browser использует встроенный Android WebView для визуализации веб-сайтов. Существуют некоторые ограничения, которые предоставляет WebView для управления настройками конфиденциальности.
Например, невозможно отключить некоторые команды JavaScript при отключении других.
- В будущем Privacy Browser переключится на форк WebView, называемый <a href="https://www.stoutner.com/category/roadmap/">Privacy WebView</a>.</p>
+ В будущем Privacy Browser переключится на форк WebView, называемый <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">Privacy WebView</a>.</p>
</body>
</html>
\ No newline at end of file
<p>Almost all websites with logins require cookies to be enabled for a user to log in.
That is how they make sure it is still you as you move from page to page on the site, and is, in my opinion, the only legitimate use for 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>If cookies are enabled but JavaScript is disabled, the privacy icon will be yellow <img class="inline" src="../shared_images/warning.svg"> as a warning.</p>
<p>Third-party cookies are set by portions of a website that are loaded from servers different from the URL at the top of the page.
There is no good reason to ever enable third-party cookies. Privacy Browser 3.8 removed the option, and even Google is planning to
- <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">disable them in the future</a>.
- On devices with Android KitKat (version 4.4, API 19), WebView does not
- <a href="https://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies(android.webkit.WebView, boolean)">differentiate
- between first-party and third-party cookies</a>. Thus, enabling cookies will also enable third-party cookies.</p>
+ <a href="https://www.theverge.com/2020/1/14/21064698/google-third-party-cookies-chrome-two-years-privacy-safari-firefox">disable them in the future</a>.</p>
<h3><svg class="header"><use href="../shared_images/web.svg#icon"/></svg> DOM Depolama</h3>
<h3><svg class="header"><use href="../shared_images/subtitles.svg#icon"/></svg> Form Verisi</h3>
- <p>Form data contains information typed into web forms, like user names, addresses, phone numbers, etc., and lists them in a drop-down box on future visits.
+ <p>Form data contains information typed into web forms, like usernames, addresses, phone numbers, etc., and lists them in a drop-down box on future visits.
Unlike the other forms of local storage, form data is not sent to the web server without specific user interaction. Beginning in Android Oreo (version 8.0, API 26),
WebView’s form data was replaced by the <a href="https://medium.com/@bherbst/getting-androids-autofill-to-work-for-you-21435debea1">Autofill service</a>.
As such, controls for form data no longer appear on newer Android devices.</p>
<p>Privacy Browser, web sitelerini oluşturmak için Android’in yerleşik WebView (Web Görünümü) sürümünü kullanır.
Gizlilik ayarlarını yönetmek için WebView’ın oluşturduğu kontrollerde bazı kısıtlamalar vardır.
Örneğin, birtakım teknolojileri devre dışı bırakırken, bazı JavaScript komutlarını etkinleştirmek mümkün değildir.
- Gelecek versiyonlarında, Privacy Browser, <a href="https://www.stoutner.com/category/roadmap/">Privacy WebView</a> adlı özel bir WebView sürümüne geçiş yapacaktır.</p>
+ Gelecek versiyonlarında, Privacy Browser, <a href="https://www.stoutner.com/category/privacy-browser-android-roadmap/">Privacy WebView</a> adlı özel bir WebView sürümüne geçiş yapacaktır.</p>
</body>
</html>
\ No newline at end of file
projects / PrivacyBrowserAndroid.git / commitdiff