I guess this is working as expected.

Can someone confirm this is expected?

It wasn't the same behavior previously.
Previously, the site would load.
Which isn't to say it was right before/or now.
A related insecure message would allow the user to select 'proceed' anyway - although not with this particular insecure https. We would see that with domains that redirect to a firewall before allowing access (I don't know the specific name for this type of redirect) but the resulting warning from Google would explain there was a problem 'do you want to proceed anyway'.

I don't really understand what you mean by "site that is insecure". Can you give us a little more detail about what's going on? Is the site's certificate signed using SHA-1, for instance? If you open the console, you should get some relevant detail.

In general, we're constantly ratcheting up our protections against various kinds of badness on the web. If you have known-insecure sites, you shouldn't be too terribly surprised when Chrome updates start surfacing that insecurity.

There's no actionable information here and no followup for 9 months. If you are still encountering problems, please open a new issue.