Trigger captive portal checks on secure DNS network failures.
These captive portal checks may occur on either HTTP or HTTPS navigations. The CaptivePortalTabHelper no longer tracks navigations that are renderer-initiated to avoid interference from link doctor and renderer-initiated reload attempts (these navigations, which can be triggered by DNS failures, may otherwise reset the tab state before a captive portal probe result is received). Bug: 10161646 Change-Id: Ia2ac3715d43e9b1be71df1dea7a1882f98033888 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870013Reviewed-by:Avi Drissman <avi@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Katharine Daly <dalyk@google.com> Cr-Commit-Position: refs/heads/master@{#737843}
Showing
This diff is collapsed.
This diff is collapsed.
Please register or sign in to comment