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

Launch Flow: Chrome "Leave site?" dialog appearing at end of launch flow #48886

Closed
ianstewart opened this issue Jan 13, 2021 · 7 comments
Closed

Comments

@ianstewart
Copy link
Contributor

Steps to reproduce the behavior

  1. Go to wp.com/new
  2. Proceed through to Editor screen
  3. Click launch button
  4. Proceed through launch flow
  5. Get to "Hooray!" screen and observe error below

Result

image

@pauljacobson
Copy link

pauljacobson commented Jan 14, 2021

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:

Screen Shot 2021-01-13 at 8 59 32 AM

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
Firefox 84.0.2 (64-bit)
Macbook Air M1 chip

I am also on macOS 11.1, using Firefox Developer Edition v85.0b7.

Source: 3641317-zd

@tbradsha
Copy link
Contributor

Also reported in 3643293-hc.

I was able to reproduce on macOS 11.1, Chrome 87.0.4280.141:

  1. Open a page.
  2. Add an image block.
  3. Update the page.
  4. Click "View page":
    image
  5. Receive the "leave page" alert:
    image

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).

@simison
Copy link
Member

simison commented Jan 22, 2021

@Automattic/good-mountain was this something that's fixed in latest Gutenberg?

@Copons
Copy link
Contributor

Copons commented Jan 22, 2021

I'm not able to repro any of the 3 different issues reported here, tested with Chrome and Firefox on MacOS 11.1.
Since the reports, a new Gutenberg version (9.7 up to 9.7.2) has been merged to .com.
At a quick glance of the changelogs, nothing seems related to this issue.

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.

@sirreal
Copy link
Member

sirreal commented Jan 22, 2021

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.

@simison
Copy link
Member

simison commented Jan 22, 2021

Thanks both! Let's close for now and be on the lookout.

@simison simison closed this as completed Jan 22, 2021
@tbradsha
Copy link
Contributor

Confirmed that I can no longer reproduce this, so let's hope it's fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants