Wrong `history.state.id` after usage of `goto`

[PatrickG]

I need a way to know if it is "safe" to use history.go(-1) (safe in the way, that the previous history entry is still my app).
I wanted to use history.state.id which is increased by 1 for every link click. So in theory, if history.state.id > 1 it is safe to use history.go(-1).
But the id in the history.state does not get increased after using goto, instead it is the same id the previous history entry has.
If you click a link after using goto the id is increased by 2.

Also, it would be helpful, if we could store some things in the history state while using goto.

[raythurnvoid]

Also, it would be helpful, if we could store some things in the history state while using goto.

I've just created a pull request
#1341