close
Skip to content

Leverage revisions in convert to blocks action #12162

@oandregal

Description

@oandregal

Is your feature request related to a problem? Please describe.

We consider "Convert to blocks" a destructive action that can be reverted: we can't guarantee perfect conversion, content may be lost although the user always has the choice to undo.

This expectation is not always clear to users, and I want to propose an approach that makes that clear while leveraging the WordPress tools we already have.

Describe the solution you'd like

After a user converts something to blocks we could show a notice saying something like:

Hey, the original block had 10.601 words and the new one has 8.021 words. Do you want to check the differences?

It will include a link to the revisions page where the user can visually spot them and take action (revert). We'll use the same notice to communicate that the process was not loosey as well.

Describe alternatives you've considered

A solution floated in some conversations was to show a message before the convert to blocks action along the lines of:

You might lose content with this action. Please, confirm.

I find this not very helpful and unnecessarily scary most of the times. The "Convert to blocks" logic does an impressive job at preserving content and transforming bad formatted HTML into a good one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions