-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Launch Flow: Chrome "Leave site?" dialog appearing at end of launch flow #48886
Comments
I have what seems to be a related issue. A user reported that when they publish a post, and then click the option in the block editor pane to the left to create a new post, they see a similar message in Firefox: I encountered this issue in the last few days, although I can't seem to reproduce it now. The user's system information is as follows: Mac OS Big Sur 11.1 I am also on macOS 11.1, using Firefox Developer Edition v85.0b7. Source: 3641317-zd |
Also reported in 3643293-hc. I was able to reproduce on macOS 11.1, Chrome 87.0.4280.141:
Note that if I cancel the alert, it'll still show the Update button as active, and I can repeat steps 3-5 indefinitely (without making any changes to the page). |
@Automattic/good-mountain was this something that's fixed in latest Gutenberg? |
I'm not able to repro any of the 3 different issues reported here, tested with Chrome and Firefox on MacOS 11.1. In the off-chance I'm missing something in the repro steps, I'd love to have a new check (at least by @ianstewart as original author) before closing this issue. |
I don't see any obviously related recent changes and it isn't highlighted in the release notes for 9.6 or 9.7, both of which received recent upgrades. It's entirely possible that it has been fixed without me being aware or finding it. I'm also unable to reproduce at this time and I think we can close. |
Thanks both! Let's close for now and be on the lookout. |
Confirmed that I can no longer reproduce this, so let's hope it's fixed! |
Steps to reproduce the behavior
Result
The text was updated successfully, but these errors were encountered: