Skip to content

Conversation

klaemo
Copy link
Contributor

@klaemo klaemo commented Aug 2, 2016

While developing a widget which is meant to be embedded into websites
via an iframe, we noticed history taking over the parent page’s
back/forward button (not a bug, just the way browser history works). We
were able to isolate the routing to the widget by using
memoryHistory.

This PR just adds a tiny note that createMemoryHistory can be useful
for a case like that.

While developing a widget which is meant to be embedded into websites
via an iframe, we noticed `history` taking over the parent page’s
back/forward button (not a bug, just the way browser history works). We
were able to isolate the routing to the widget by using
`memoryHistory`.

This PR just adds a tiny note that `createMemoryHistory` can be useful
for a case like that.
@timdorr
Copy link
Member

timdorr commented Aug 2, 2016

Thanks!

@timdorr timdorr merged commit e91af71 into remix-run:master Aug 2, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
brophdawg11 pushed a commit that referenced this pull request Mar 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants