-
Notifications
You must be signed in to change notification settings - Fork 56
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
Project issue: Unsupported blocks fallback mechanism #2358
Labels
Comments
guarani
changed the title
Unsupported blocks fallback mechanism
Master issue: Unsupported blocks fallback mechanism
Jun 11, 2020
This was referenced Jun 16, 2020
2 tasks
3 tasks
3 tasks
3 tasks
This was referenced Jun 30, 2020
This was referenced Jul 10, 2020
Closed
guarani
changed the title
Master issue: Unsupported blocks fallback mechanism
Project issue: Unsupported blocks fallback mechanism
Jul 15, 2020
We are finishing the focus on this feature after merging the main PRs (WordPress/gutenberg#21150 WordPress/gutenberg#25238) and the most important side PRs described on this ticket. What's left will be worked later on after new assignments are made. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Implement a fallback mechanism for unsupported blocks. A user who encounters an unsupported blocks should be able to view and edit the block in question, without leaving the mobile Gutenberg editor.
Required to ship to the public:
UI tests PRUI tests PR/rn-gutenberg-bridge
(discussion).\n
issueExtras:
To Dos:
Additional infomation
The text was updated successfully, but these errors were encountered: