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.

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

Backport "Fix popup not opening" #8446

Merged
merged 1 commit into from
Apr 29, 2020

Conversation

Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Apr 28, 2020

This is a backport of #8314. Here's the original description:

MetaMask would sometimes get into a state where the notification popup would never open. This could happen if the notification window was closed shortly after being opened. After this happened, no popups would show up until after the extension was reset.

This was happening because the background thought the popup was already open. The variable it uses to track whether the popup was open or not was being set to true immediately after the background asked the browser to open a new window, before a handler was attached that could respond to the window being closed.

Removing this line seems to solve the problem.

This line was added originally in #5437, which dealt with batch transactions. Batches of transactions seem to work just fine without this line though (from local testing), and I can't think of why this would be required.

Closes #7051

@Gudahtt Gudahtt force-pushed the backport-fix-popup-not-opening branch from 2e3064f to aa07ef0 Compare April 28, 2020 17:24
@metamaskbot
Copy link
Collaborator

Builds ready [aa07ef0]

This is a backport of #8314. Here's the original description:

MetaMask would sometimes get into a state where the notification popup
would never open. This could happen if the notification window was
closed shortly after being opened. After this happened, no popups would
show up until after the extension was reset.

This was happening because the background thought the popup was already
open. The variable it uses to track whether the popup was open or not
was being set to `true` immediately after the background asked the
browser to open a new window, before a handler was attached that could
respond to the window being closed.

Removing this line seems to solve the problem.

This line was added originally in #5437, which dealt with batch
transactions. Batches of transactions seem to work just fine without
this line though (from local testing), and I can't think of why this
would be required.

Closes #7051
@Gudahtt Gudahtt force-pushed the backport-fix-popup-not-opening branch from aa07ef0 to aec1c99 Compare April 28, 2020 18:57
@metamaskbot
Copy link
Collaborator

Builds ready [aec1c99]

@Gudahtt Gudahtt requested a review from a team April 28, 2020 19:22
@Gudahtt Gudahtt merged commit 2a51399 into Version-v7.7.9 Apr 29, 2020
@Gudahtt Gudahtt deleted the backport-fix-popup-not-opening branch April 29, 2020 04:57
@metamaskbot metamaskbot mentioned this pull request May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants