Why do you expect the forward button to be disabled? Desktop has the same behavior (forward button navigates to page #1).

Because in my opinion I have started a new navigation (which didn't complete because there is a problem with the certificate). I don't expect the navigation stack to remain the same.

Emily, Charlie, do you think this is a bug or WAI? If a bug then we probably should fix it for all platforms.

I don't care too much about this either way -- I think either behavior is fine. My guess is that the current behavior was more or less an accident of how interstitials work and that nobody thought too hard about it. (Charlie may have been around at the time and might actually know one way or another.)

In any case, this behavior is going to change on non-iOS platforms with the committed interstitial refactor. Interstitials will clear the navigation stack like a normal navigation, or like a net error page. (https://docs.google.com/document/d/1rEBpw5V-Nn1UIi8CIFa5ZZvwlR08SkY3CogvWE2UMFs/edit) It'll take a while to get around to it, but we should eventually convert iOS to a similar design where interstitials work more like net error pages.

Thanks Emily. Do we have a bug for "committed interstitials", so I can block this bug on "committed interstitials" bug? 

Yep, it's 448486.

The current behavior probably wasn't a conscious decision, but it's what I would expect given how interstitials work (i.e., as overlays).  The forward history is not cleared until a new navigation commits, and an interstitial page is not a commit (at least until the refactor estark@ mentioned in issue 448486).  It's similar to doing a slow navigation and clicking forward before it completes.

So I'd say it's working as intended for now, and the forward history will be cleared as gambard@ expected after we switch interstitials from overlays to committed pages.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot