UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36

Steps to reproduce the problem:
1. Navigate to a site with an invalid https certificate that is also flagged by SafeBrowsing as phishing.
2. The certificate error pops up first (although this is not always the case). Attempting to proceed through doesn't navigate. (The requests shows as (canceled) in Dev Tools, further clicks do nothing)
3. Reload the page to get past http interstitial and load the Safe Browsing one.
4. Click through to visit the site.

What is the expected behavior?
Clicking through the first interstitial could show the second one without a reload needed. 

What went wrong?
A reload is needed to get past the interstitial.

Did this work before? N/A 

Chrome version: 68.0.3440.75  Channel: stable
OS Version: 
Flash Version: 

Having seen Issue 448486, I tried this with the Committed
Interstitials flag enabled. It made the Safe Browsing interstitial come first and made more requests appear in Dev Tools (with a ERR_CERT_COMMON_NAME_INVALID failure) but did not fix the problem, the page still required a reload.

Vid: https://youtu.be/8Jwniuei5B8
Vid w/ Committed Interstitials: https://youtu.be/JZrGXpO4wbc