clarification about WebView compared to Chromium
This commit is contained in:
parent
32c9548127
commit
314d518d3d
@ -948,14 +948,15 @@
|
|||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<p>Vanadium does not make connections not requested by the app as part of providing
|
<p>Unlike Chrome/Chromium, Vanadium does not make connections not requested by
|
||||||
the WebView implementation in the OS. If you choose to use it as your browser, it
|
the app as part of providing the WebView implementation in the OS. If you
|
||||||
performs similar connections as the ones performed by the OS above. It does not send
|
choose to use it as your browser, it performs similar connections as the ones
|
||||||
any identifying information to servers, etc. but rather fetches some static assets
|
performed by the OS above. It does not send any identifying information to
|
||||||
like dictionaries when triggered by usage of the app. We're working on eliminating
|
servers, etc. but rather fetches some static assets like dictionaries when
|
||||||
everything unnecessary and making our servers the default for handling anything that
|
triggered by usage of the app. We're working on eliminating everything
|
||||||
cannot simply be shipped with Vanadium for one reason or another such as requiring
|
unnecessary and making our servers the default for handling anything that
|
||||||
quicker updates.</p>
|
cannot simply be shipped with Vanadium for one reason or another such as
|
||||||
|
requiring quicker updates.</p>
|
||||||
</article>
|
</article>
|
||||||
|
|
||||||
<article id="other-connections">
|
<article id="other-connections">
|
||||||
|
Loading…
x
Reference in New Issue
Block a user