samartnik
76325e72f2
Chromium change: https://github.com/chromium/chromium/commit/47c3fd7b00c12e5fe3b0cc263f58e6e6be9d98f3 Redefine what constitutes a redirect in RedirectHandler I've started using the terminology "navigation chain" as "redirect" is far too overloaded a term. Before this change, RedirectHandler tries to figure out what constitutes a new navigation started by the user, which ends up being super complicated and sometimes incorrect as it looks at when the user last touched the screen (which could break up what should have been considered a navigation chain). Instead, this change defines anything coming from the renderer without a user gesture (and server redirects) as part of the navigation chain. I don't expect this to break any web pages, but will be launching with a finch flag to restore the old behavior in case things unexpectedly break. For testing purposes, the finch flag will be on for bots API level N and below, and off for API level above N, so both paths get bot coverage. I also marked fallback URL navigation as renderer initiated, as this more closely matches reality (the navigation and URL were initiated by the renderer), and matches the previous implementation which did consider fallback URLs as part of the same navigation chain. It's also worth noting that WebLayer, prior to this change, already doesn't use the user touching the screen to reset the navigation chain. This change should better align Chrome and WebLayer on External Navigation handling. Bug: 1288578