Like

 Issue 678336  has been merged into this issue.

https://cs.chromium.org/chromium/src/chrome/browser/ui/views/omnibox/omnibox_view_views.cc?l=609

   const bool strike = (security_level_ == security_state::DANGEROUS);

We could test if security_info.malicious_content_status != security_state::MALICIOUS_CONTENT_STATUS_NONE, but what happens if a site has both malicious content AND bad HTTPS? Does content_with_cert_errors_status note certificate problems for the main page itself, or only its subdownloads?

This is a plumbing project of questionable value (pedantically, our behavior is "wrong" but making dangerous pages look extra dangerous isn't necessarily bad).

The way to check for a certificate issue is to look at IsCertStatusError(security_info.cert_status). But the problem is that the omnibox code doesn't have a SecurityInfo, it only has the SecurityLevel that it grabbed via GetToolbarModel()->GetSecurityLevel(false). That model gets the answer from the ToolbarModelDelegate, which computes it from the SecurityInfo retrieved by the SecurityStateTabHelper for the current WebContents. ChromeToolbarModelDelegate::GetSecurityLevel().