Level 7
In an attempt to improve the security of its users, the Chrome browser will soon start blocking insecure downloads on HTTPS pages, Google announced.

The plan, which the Internet giant laid out this week, is expected to be completed sometime in the fall, when Chrome 86 arrives.
The announcement comes just days after the release of Chrome 80, which by default blocks mixed audio and video resources if they cannot be automatically upgraded to HTTPS. The same will happen with image files in Chrome 81, which is expected to be released to the stable channel in March 2020.
In the long term, Google’s plan is to block all insecure sub resources on secure pages, as they represent a risk for users. Files that are downloaded insecurely could be replaced by attackers with malware, or exposed to eavesdroppers.

“To address these risks, we plan to eventually remove support for insecure downloads in Chrome,” the Internet giant says.
In the initial phase, the focus is on insecure downloads started on secure pages, and the first step is to display warnings. The restrictions for mixed content downloads, Google says, will be pushed to all desktop platforms first.

Executable files will be impacted first, with Chrome 82 displaying a warning on them and Chrome 83 blocking them.

Sampei Nihira

Level 6
There is something wrong with the information in the article.
This is much more detailed:

And in fact it seems to me that mixed audio video content is not blocked in Chrome 80.
As verified by the test below:

Microsoft Edge/Chromium also behaves the same way.
My New Moon performs much better on this test.(y)(y)(y)(y)
Last edited: