AlgoSigner is not added to `window` global in certain cases

Open gabrielkuettel opened this issue 3 years ago • 1 comments

I believe this may be a related closed issue: https://github.com/PureStake/algosigner/issues/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.

Jan 31 '23 20:01 gabrielkuettel

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

Feb 14 '23 14:02 janmarcano