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.
This commit is contained in:
parent
4e21632084
commit
4c7a0b59c0
@ -521,12 +521,6 @@
|
|||||||
<li>HTTP fallback: http://www.google.com/gen_204</li>
|
<li>HTTP fallback: http://www.google.com/gen_204</li>
|
||||||
<li>HTTP other fallback: http://play.googleapis.com/generate_204</li>
|
<li>HTTP other fallback: http://play.googleapis.com/generate_204</li>
|
||||||
</ul>
|
</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>
|
||||||
<li>
|
<li>
|
||||||
<p>DNS connectivity and functionality tests</p>
|
<p>DNS connectivity and functionality tests</p>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user