Currently the navigationId is stores in history.state. But with #27198 users can now set data into history.state. If the developer were to set a navigationId property it would get clobbered by Angular's setting of the same field.

We would like to deprecate (or maybe just remove since we never put it in the public API) the navigationId and add another data structure inside history.state that can be specific to Angular. This way, when we want to add more data to history.state, we have an object key under which we can do so. One idea is to add the scroll position to history.state rather than storing it in the router. This would allow us to preserve scroll position through hard browser refreshes.

FW-771