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
What is the current behavior and expected behavior?
Current behavior: On first page load (e.g new window of chrome incognito mode) web3Enable function could freeze on it's execution. Expected behavior: URL authorization window popup is shown when web3Enable function is fired. STR:
And the button which will execute it on click.
4. Open new incognito window in chrome and go to the app page.
5. Click the connection button. You'll see no action, even though it will be "Web3 Injected: true" in the console.
6. Refresh the page and try again. You'll see normal behavior from now on.
Couldn't be reproduced in firefox browser.
What is the motivation for changing the behavior?
User should be able to connect the extension even on new incognito window.
Please tell us about your environment:
OS: macOS 13.2.1
Browser: Chrome 111.0.5563.64 (Official Build) (arm64), new incognito window, all extensions except for polkadot-js are disabled
Extension version: 0.44.1
Code setup: CRA 5.0.1
Version: 0.44.1
Environment:
Node.js
Browser
Other (limited support for other environments)
Language:
JavaScript
TypeScript v4.9.5
Other
The text was updated successfully, but these errors were encountered:
attemka
changed the title
Enable promise stalled on first page load in extension-dapp
web3Enable promise stalled on first page load in extension-dapp
Mar 21, 2023
Current behavior: On first page load (e.g new window of chrome incognito mode) web3Enable function could freeze on it's execution.
Expected behavior: URL authorization window popup is shown when
web3Enable
function is fired.STR:
And the button which will execute it on click.
4. Open new incognito window in chrome and go to the app page.
5. Click the connection button. You'll see no action, even though it will be "Web3 Injected: true" in the console.
6. Refresh the page and try again. You'll see normal behavior from now on.
Couldn't be reproduced in firefox browser.
User should be able to connect the extension even on new incognito window.
Please tell us about your environment:
Version: 0.44.1
Environment:
Language:
The text was updated successfully, but these errors were encountered: