Chrome block subresources requests that target "legacy" protocol (like "ftp") when the main document is not served from a "legacy" protocol.
With PlzNavigate, it happens after the request has been made instead of before.
What steps will reproduce the problem?
(1) Navigate to data:text/html,<iframe src="ftp://ftp.funet.fi/not_found.html"></iframe>
What is the expected result? (Without --enable-browser-side-navigation)
A blank page is displayed.
What happens instead? (With --enable-browser-side-navigation)
An error page "The webpage at ftp://ftp.funet.fi/not_found.html might be temporarily down or it [...]"
Comment 1 by bugdroid1@chromium.org
, Aug 30 2017