You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.
I believe this may be a related closed issue: #396
In some cases, it appears that AlgoSigner does not attach itself to the window global. It seems to happen after a page refresh. But it's intermittent and hard to debug.
Also, noticed that AlgoSigner does not inject itself to window if opening a blank tab, or on localhost. Is that behavior documented anywhere?
Just looking for more information so I can figure out how to reproduce/debug this issue. Thanks.
The text was updated successfully, but these errors were encountered:
we'll try to take a second look into the injection issue on refreshes
regarding it not injecting on a blank tab:
we inject the AlgoSigner object on all the URL schemes that Chrome allows us to via the content script, Google has their own criteria on what is a valid or invalid URL scheme
for the localhost issue, you could try with 127.0.0.1 as that does appear to match according to the Chrome docs
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I believe this may be a related closed issue:
#396
In some cases, it appears that
AlgoSigner
does not attach itself to thewindow
global. It seems to happen after a page refresh. But it's intermittent and hard to debug.Also, noticed that
AlgoSigner
does not inject itself towindow
if opening a blank tab, or onlocalhost
. Is that behavior documented anywhere?Just looking for more information so I can figure out how to reproduce/debug this issue. Thanks.
The text was updated successfully, but these errors were encountered: