Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about CollectivesStack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack Internalhistory.back() should do the trick.
window.history.back() documentation at MDNwindow.history.back() documentation at MDN
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
history.back() should do the trick.
window.history.back() documentation at MDN
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
history.back() should do the trick.
window.history.back() documentation at MDN
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
history.back()history.back() should do the trick.
window.history.back() documentation at MDN
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
history.back() should do the trick.
window.history.back() documentation at MDN
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
history.back() should do the trick.
window.history.back() documentation at MDN
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
history.back() should do the trick.
back() documentation at w3Schoolswindow.history.back() documentation at MDN
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
history.back() should do the trick.
back() documentation at w3Schools
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
history.back() should do the trick.
window.history.back() documentation at MDN
As an aside, it's bad user experience if you do this unexpectedly on the user. For example, I enter in an invalid credit card number, and you take me back one page, instead of letting me fix the mistake.
So while it's possible to use javascript to manipulate the history stack, it's better to only do so if it makes sense in the context current users actions.
