🚀 Feature Request
Currently Playwright supports both page.goBack() and page.goForward(), but seems to lack the other option that window.history.go() supports, which is multiple history navigations in one go.
Not sure if it even makes sense to keep both the goBack()/goForward(), or if there should be just .go(delta: number, options: {...}).
Might also make sense to expose the entire history API, and if possible more extensively than is allowed by JS on a page, which doesn't have access to the URL's, etc. Though I'm not sure how Playwright instruments the browser, so it might not have any more access than JS on page does.
Example
No response
Motivation
Allows to better simulate user behavior where user navigates multiple history pages.
🚀 Feature Request
Currently Playwright supports both
page.goBack()andpage.goForward(), but seems to lack the other option thatwindow.history.go()supports, which is multiple history navigations in one go.Not sure if it even makes sense to keep both the
goBack()/goForward(), or if there should be just.go(delta: number, options: {...}).Might also make sense to expose the entire history API, and if possible more extensively than is allowed by JS on a page, which doesn't have access to the URL's, etc. Though I'm not sure how Playwright instruments the browser, so it might not have any more access than JS on page does.
Example
No response
Motivation
Allows to better simulate user behavior where user navigates multiple history pages.