Visual revisions: highlights entire Classic Block as different

Why this is a good first issue

The issue requires modifying how visual revisions handle Classic Block changes without clear implementation details.

AI Summary

The problem is that visual revisions highlight entire Classic Blocks as changed, making it hard to see specific content changes. The solution needs to either show individual changes within Classic Blocks or provide a fallback message. The main blocker is understanding how visual revisions interact with Classic Blocks.

Issue Description

Description

When using visual revisions, if a Classic Block is in the content and has been changed, the entire block is highlighted has having been changed.

I understand why: it's a block and it's been changed :) but in the context of a revision history, it's unhelpful if there is a lot of content in that Classic Block. For example, if an entire blog post is written in a single Classic Block, the visual revisions essentially become useless as they don't show any specific content change.

For a fix, if flagging individual changes within the Classic Block isn't an option, I'd almost suggest that a message prompting folks back to classic revisions in this case would be the most useful.

Step-by-step reproduction instructions

Write a new post
Insert a Classic Block
Save post, and then make changes
View visual revisions for the post
Note how none of the individual changes are visible, only that the entire Classic Block has changed

Screenshots, screen recording, code snippet

No response

Environment info

WP 7.0-beta5
Custom theme

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

Please confirm which theme type you used for testing.

Block
Classic
Hybrid (e.g. classic with theme.json)
Not sure

GitHub Labels

[Type] Bug[Block] Classic[Feature] History