Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When using navigator and navigateTo - the contentframe don't need to reload if its not navigating away from the microservice #189

Open
einari opened this issue Apr 21, 2021 · 0 comments
Open

When using navigator and navigateTo - the contentframe don't need to reload if its not navigating away from the microservice #189

einari opened this issue Apr 21, 2021 · 0 comments

Comments

@einari
Copy link
Contributor

einari commented Apr 21, 2021 •
edited
Loading

The ContentFrame will make the iframe reload when a URL changes, even though its for the same Microservices.
Expected behavior is that it does not do that and instead updates the top level URL seen in the browser addressbar and then the location for the inner iframe window to reflect the prefixed version.
@einari einari changed the title When using navigator and navigateTo - if the query parameters are changing, we don't want to reload the content frame When using navigator and navigateTo - the contentframe don't need to reload if its not navigating away from the microservice Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@einari