-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Gutenberg/allow unsupported block editor on atomic sites #12405
Gutenberg/allow unsupported block editor on atomic sites #12405
Conversation
Generated by 🚫 dangerJS |
You can trigger optional UI/connected tests for these changes by visiting CircleCI here. |
You can test the changes on this Pull Request by downloading the APK here. |
Hey @marecar3 I'm having trouble with the build. I've downloaded Version pr-12405-build-60636, which looks like the correct build, but when I log into a regular WP.com site, the bottom sheet is missing the edit options. |
Re-tested on Galaxy S10 running Android 10 with new build 60664. (Note, I'm using the updated unsupported block sample HTML found here: wordpress-mobile/test-cases#42 since there are changes to the test cases that haven't been merged yet.) |
Description: The Unsupported Block Editor feature was disabled on sites connected via Jetpack because of an issue requesting cookies from those sites without having login credentials other than WP.com credentials.
This inadvertently blocked Atomic sites as well, which are also connected via Jetpack. Atomic sites, being WP.com sites, don't have the cookie issue so this PR enables this feature on those sites.
GB-Mobile PR: wordpress-mobile/gutenberg-mobile#2476
GB PR: WordPress/gutenberg#23830
Addresses: wordpress-mobile/gutenberg-mobile#2470
To test: perform the Unsupported Block test cases 1 to 4.
PR submission checklist:
RELEASE-NOTES.txt
if necessary.