summaryrefslogtreecommitdiff
path: root/static/faq.html
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2020-11-27 03:14:23 -0500
committerDaniel Micay <danielmicay@gmail.com>2020-11-27 03:14:23 -0500
commit4c7a0b59c0be37de9ecba867b140302eb09ec70b (patch)
tree380acc7d667eba0ba87be0f26dcc4eb01f2b93fa /static/faq.html
parent4e2163208426f146ad6b1b32d05ea067e160e952 (diff)
Chromium defers connectivity checks to the OS now
Vanadium needs to address several regressions caused by Chromium changes but this should no longer be a problem.
Diffstat (limited to 'static/faq.html')
-rw-r--r--static/faq.html6
1 files changed, 0 insertions, 6 deletions
diff --git a/static/faq.html b/static/faq.html
index 021591d1..fda37419 100644
--- a/static/faq.html
+++ b/static/faq.html
@@ -521,12 +521,6 @@
<li>HTTP fallback: http://www.google.com/gen_204</li>
<li>HTTP other fallback: http://play.googleapis.com/generate_204</li>
</ul>
-
- <p>Similar connectivity checks are also performed by Vanadium in the browser
- app, but not the WebView. This matches the behavior of Chrome and Chromium. In
- the future, we plan to have it follow our OS configuration option by having it
- switch between the GrapheneOS server and blending in with Chrome based on the
- user's choice.</p>
</li>
<li>
<p>DNS connectivity and functionality tests</p>