Trailing slashes are stripped from route URLs, creating two history entries and breaking the back button in the process #7829
Labels
Comments
reneweb
pushed a commit
to reneweb/angular
that referenced
this issue
Apr 4, 2016
…ormalized path Make sure the same path is not added multiple times to the history. It is replacing the state, instead of skipping it completely, because the current path in the browser might not be normalized, while the given one is normalized. Closes angular#7829
3 tasks
reneweb
pushed a commit
to reneweb/angular
that referenced
this issue
Apr 6, 2016
…ormalized path Make sure the same path is not added multiple times to the history. It is replacing the state, instead of skipping it completely, because the current path in the browser might not be normalized, while the given one is normalized. Closes angular#7829
reneweb
pushed a commit
to reneweb/angular
that referenced
this issue
Apr 7, 2016
…ormalized path Make sure the same path is not added multiple times to the history. It is replacing the state, instead of skipping it completely, because the current path in the browser might not be normalized, while the given one is normalized. Closes angular#7829
reneweb
pushed a commit
to reneweb/angular
that referenced
this issue
Apr 7, 2016
…ormalized path Make sure the same path is not added multiple times to the history. It is replacing the state, instead of skipping it completely, because the current path in the browser might not be normalized, while the given one is normalized. Closes angular#7829
reneweb
pushed a commit
to reneweb/angular
that referenced
this issue
Apr 8, 2016
…ormalized path Make sure the same path is not added multiple times to the history. It is replacing the state, instead of skipping it completely, because the current path in the browser might not be normalized, while the given one is normalized. Closes angular#7829
KiaraGrouwstra
pushed a commit
to KiaraGrouwstra/angular
that referenced
this issue
Jun 10, 2016
…ormalized path Make sure the same path is not added multiple times to the history. It is replacing the state, instead of skipping it completely, because the current path in the browser might not be normalized, while the given one is normalized. Closes angular#7829 Closes angular#7897
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to reproduce and a minimal demo of the problem
Current behavior
The path changes to
/#/list/and then immediately to/#/list, creating two history entries and breaking the back button in the process.Expected/desired behavior
The redirection shouldn't occur. The trailing slash shouldn't have been stripped.
Other information
Currently the only workaround I know is to create routes not ending with a slash; the problem doesn't exist then.
The text was updated successfully, but these errors were encountered: