ContentSerializedNavigationDriver::Sanitize() contains a bunch of checks for manipulating SerializedNavigationEntry state. Do they make sense when the code is in a component? Should Sanitize() delegate to the embedder?
We copied / moved a bunch of WebUI URL constants from chrome/ to content/ to make the code in Sanitize() work. There's a few that ended up getting hard coded. If we do decide to delegate to the embedder, we should re-examine the WebUI constants, e.g. kChromeUIHistoryHost, and decide if they should live in content/ or chrome/.
Comment 1 by thestig@chromium.org
, Mar 15 2017