pasko@: Can you explain the connection to AMP prerenders from the bug description? My impression was that "AMP prerender" is unrelated to Chrome's prerendering code-- AMP loads the next page in an iframe and then shows it, unlike loading it in a new WebContents and then swapping WebContents. (Maybe you were referring to something else?)
I know there's more recent work on portals in issue 865565 which might be closer to Chrome's prerender code, but I don't know if that's a blocker for removing the old code or not. +lfg for that.
In August of 2017, AMP still used a prerender from the SRP in AGSA custom tabs. That's no longer the case, as that path was migrated to use a background tab instead.
IIUC, the iframe stuff is used when AMP loads from a SRP in Chrome. So that was always a separate issue. The AMP use pasko@ referred to was the custom tabs flow.
Comment 1 by pasko@chromium.org
, Aug 16 2017