Proposal: Allow navigation with replacement enabled in additional, optional cases

[natechapin]

Chromium is experimenting with ways to reduce the frequency of nuisance history entries . The rules we're trending toward in our experiment are to override the default behavior and navigate with replacement enabled if (1) the source browsing context has never experienced user activation and (2) the source browsing context's active document has been the active document for less than a threshold time (5 seconds).

I propose adding a step to the navigate algorithm that optionally allows the navigation to be performed with replacement enabled, regardless of the behavior given when the navigate algorithm was invoked.

[chrishtr]

I'm wondering: what are the legitimate use cases of pushing a history entry on load of a URL?
Is it to handle client-side "redirects"? Or is there another one?

[natechapin]

The chromium intent thread provided an example of a way this behavior would break legitimate existing use cases, so I'm not planning on pursuing this further.