-
Notifications
You must be signed in to change notification settings - Fork 58
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
Buttons blocks added using the block editor on WordPress.com show up as "Unsupported" #1956
Comments
Hello @designsimply, please notice that Buttons are not supported, but Button itself is supported. Could you please confirm that on the web you've added Button (however it should not be possible since we are not supporting it) instead of Buttons? |
I see! On the web I did add the "Buttons" block but didn't realize it would work any differently than the "Button" block. 😁 I also see that work is happening at #1790 to support the Buttons block, which should close this issue when it's completed. |
Exactly, working on it to ship it asap! 😁 |
Since this is opened due to a misunderstanding do you see value keeping this one open? @designsimply ? This is trackable by #1790 |
I think it still feels like a bug for the Buttons block (even though it's expected since it's not technically supported yet). I would leave it open and let it be closed by 1790. That way, if others find the same problem they will hopefully search and see that this issue is being worked on already. Note: I also updated the title to say "Buttons" block instead of "Button" block. |
Closing since Buttons block is merged on mobile a while ago. |
Steps to reproduce:
Result: button blocks added using the block editor on WordPress.com show up as "Unsupported" in the block editor in the iOS app.
Note: this problem only happens with button blocks created with Calypso Gutenberg. Buttons added to Jetpack or self-hosted sites using Gutenberg do not have the same problem.
Tested with WPiOS 14.3.0.0 TestFlight beta on iPhone 6S iOS 13.3.1.
The text was updated successfully, but these errors were encountered: