What's the meaning of broken HTTPS in chrome?

The information in chrome clearly indicates why it is broken https: not because the certificate is wrong but because of mixed content. It also shows you which site the non-https content would have been loaded from (see "Non-Secure Origins") and offers you to see more details.

I tried the same thing, but from Safari, and nothing is wrong, Different browsers sometimes have different ideas of how dangerous specific types of mixed content are. For example some might accept if fonts are loaded insecurely while others require these to be loaded securely too. But the general trend is that everything has to be loaded securely. I can view the certificate and it says connection is secure with no problem. It's not a problem with the certificate but with the mixed content. My main question is, How is this happening to be "https" when it's broken ? The protocol spoken to the main resource is still https. Would that be secure if I opened the VPN, with or without the web to be https ? A VPN only protects the connection to the VPN endpoint. Since the VPN endpoint is not the target server this would not solve this problem.