There is something strange how Angular pops the state.
history.state is gone and so is
router.getCurrentNavigation().extras.state, which is unfortunate. I’d expect that they would be retrieved when
We plan (there are still some issues when passing state on non
a elements) to use this mechanism only for one…
You mean subscribing to
router.events in component’s constructor and getting the data from
router.getCurrentNavigation().extras.state ? You could do that, but then you’ll have new dependency in your component and you’ll have not empty constructor which can hinder unit testing.