You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a block parses HTML markup, it also tries to validate the data by re-serializing and comparing the result. Unfortunately blocks currently compare with an exact string match. Even a small whitespace for change for completely equivalent markup/styling, is enough to cause the following scary error:
Clicking on the primary action usually isn't what the user wants. It converts the previously nice to understand block into a plain HTML block:
The best action is usually "Attempt Block Recovery" or "Convert to Blocks"
Traditionally WP allows manipulation of content from a variety of filters/customizations, so this is a very easy case to fall into.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.
Breaking out an actionable piece of #37230
This is a two parter:
Context
When a block parses HTML markup, it also tries to validate the data by re-serializing and comparing the result. Unfortunately blocks currently compare with an exact string match. Even a small whitespace for change for completely equivalent markup/styling, is enough to cause the following scary error:
Clicking on the primary action usually isn't what the user wants. It converts the previously nice to understand block into a plain HTML block:
The best action is usually "Attempt Block Recovery" or "Convert to Blocks"
Traditionally WP allows manipulation of content from a variety of filters/customizations, so this is a very easy case to fall into.
The text was updated successfully, but these errors were encountered: