Skip to content

window.location.href not restored when closing details window #118

New issue

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

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

Already on GitHub? # to your account

Closed
Zaitsev opened this issue Nov 4, 2019 · 10 comments
Closed

window.location.href not restored when closing details window #118

Zaitsev opened this issue Nov 4, 2019 · 10 comments
Assignees

Comments

@Zaitsev
Copy link

Zaitsev commented Nov 4, 2019

I'm using sectorjs as module in react electron app with hash router
Spector opens results window on capture

image
window.location.hash === #/anomaly_gl/history which is right hash for captured page
bu after clicking Close hash becomes #/. Since it is react hash router, this renders another page.

@sebavan
Copy link
Member

sebavan commented Nov 4, 2019

Hello, could you detali a bit more the issue and when this happens ?

thanks,

@Zaitsev
Copy link
Author

Zaitsev commented Nov 4, 2019

Just updated issue

@sebavan
Copy link
Member

sebavan commented Nov 4, 2019

Oh what should the url be to not enter in conflict with yours ???

@Zaitsev
Copy link
Author

Zaitsev commented Nov 4, 2019

URL should be the same as it was, btw url by itself is OK, but window.location.hash wes cleared
ie symbols after '#' in hash should not be changed
image

@sebavan
Copy link
Member

sebavan commented Nov 4, 2019

Cool thanks.

@Zaitsev
Copy link
Author

Zaitsev commented Nov 4, 2019

Offtop: is there any way to move spector to devtools tab like react and redux devtools did it. IMHO spectro IS devtool and having it there will allow to display results in-page and not spoil web-toolbar?
image

@sebavan
Copy link
Member

sebavan commented Nov 4, 2019

might be good as an option, I am totally not opposed to it if you fancy doing a PR ?

@Zaitsev
Copy link
Author

Zaitsev commented Nov 4, 2019

It would take me too much time (never did any chrome extensions....)

@Zaitsev
Copy link
Author

Zaitsev commented Nov 4, 2019

URL should be the same as it was, btw url by itself is OK, but window.location.hash wes cleared
ie symbols after '#' in hash should not be changed

I'm not sure, but if hash is affected then location.search could be affected too , ie ?param1=val&param2=val2 part of uri

@sebavan
Copy link
Member

sebavan commented Nov 5, 2019

Ok I ll try to do the url changes soon and keep the other one for later as a feature request. I won t be available before monday next week though when I should do the logo migration as well.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants