Skip to content

Style revisions: Compare the selected revision with the current version side by side - #85288

Merged
im3dabasia merged 10 commits into
trunkfrom
add/style-revisions-code-diff
Nov 6, 2026
Merged

im3dabasia merged 10 commits into
trunkfrom
add/style-revisions-code-diff

Conversation

@im3dabasia

@im3dabasia im3dabasia commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

What?

Part of #53484

Compares the selected style revision with the current version side by side, as a visual preview or as a code diff of the styles and settings, under a header naming each.

Why?

  • The revisions list says which areas changed ("Colors, Typography") but not the values.
  • Subtle changes are hard to spot by switching between previews.
  • Implements the comparison view approved in the issue, for Style revisions.

How?

  • Lives in the editor's styles canvas, so both site editors get it.
  • The post revisions code diff is refactored to share its table shell; its output is unchanged.
  • Keys are sorted before diffing, so ordering differences don't show as changes.
  • The current version is compared by id, as the sidebar does, since the revisions and global styles endpoints need not serialize the same styles identically.
  • "Matches" uses areGlobalStylesEqual, the same check as the sidebar's Apply button.
  • Selecting the current version shows a single preview rather than the same styles twice.
  • Visual panes stack when the canvas is narrow; the code view stays side by side.
  • When the canvas is narrow, the previews stack with the current version first, as in the revisions list, so the view toggle stays in the top row.
  • When comparing visually, scrolling either preview scrolls the other to the same relative position.

Notes for review

  • Side by side renders the template twice, once per styles config; that's inherent to the comparison, as with the Style Book's examples.
  • The focus-return ref moved from the preview iframe to the wrapper, which now holds both previews.
  • The header shows the full date where the sidebar shows a relative one, as in the mockup.
  • The sidebar keeps the current style revisions list; the mockup's sidebar was drawn for post revisions.
  • The close button stays, since the v1 canvas is closed from there.
  • Revisions beyond the first 100 can't be compared; that's the canvas's existing limit.

Testing Instructions

  1. In the Site Editor, change a style and save; change it again and save.
  2. Open Styles → Revisions and select the older revision.
  3. Visual: the selected revision and the current version appear side by side, each with its own styles.
  4. Code: the old value is marked removed, the current one added, side by side.
  5. Select the newest revision: a single preview, and Code says it matches the current styles.
  6. Narrow the canvas (open the sidebar or shrink the window): the previews stack; the code view stays split.
  7. Repeat in the extensible site editor's styles route: no gap where the close button would be.

Testing Instructions for Keyboard

  1. Tab to the Visual / Code toggle and switch views with the arrow keys.
  2. Tab into each preview and into the code view; each is focusable and labelled.

Screenshots

Visual Code Stacked
image image image
Screen.Recording.2026-10-21.at.5.49.05.PM.mov

Use of AI Tools

Written with Claude Code; reviewed and tested manually in the site editor, with e2e runs in both site editors.

@im3dabasia im3dabasia self-assigned this Oct 21, 2026
@github-actions github-actions Bot added the [Package] Editor /packages/editor label Oct 21, 2026
@im3dabasia im3dabasia added [Feature] History History, undo, redo, revisions, autosave. [Type] Enhancement A suggestion for improvement. and removed [Package] Editor /packages/editor labels Oct 21, 2026
@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

🤖 PR meta 🤖

Preview in WordPress Playground

🎉 Props

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: im3dabasia <im3dabasia1@git.wordpress.org>
Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: jasmussen <joen@git.wordpress.org>
Co-authored-by: tellthemachines <isabel_brison@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

Updated as activity occurs, without notifying anyone named here. Add the props-bot label to refresh.

📦 Bundle size

Size Change: +4.35 kB (+0.05%)

Total Size: 8.62 MB

📦 View Changed
Filename Size Change
build/scripts/editor/index.min.js 567 kB +1.66 kB (+0.29%)
build/styles/editor/style-rtl.css 31.4 kB +650 B (+2.11%)
build/styles/editor/style-rtl.min.css 27.1 kB +695 B (+2.63%)
build/styles/editor/style.css 31.5 kB +654 B (+2.12%)
build/styles/editor/style.min.css 27.1 kB +695 B (+2.63%)

be58dba Run

⚡ Performance

Show the results

Client side metrics exclude the server response time.

front-end-block-theme

Metric 29df945 trunk % Change
timeToFirstByte 43.1 ms +12.53% -2.44% 43.15 ms +10.89% -5.56% -0.12%
largestContentfulPaint 76 ms +5.26% -10.53% 72 ms +11.11% -5.56% 5.56%
lcpMinusTtfb 28.5 ms +12.11% -6.14% 27.6 ms +3.44% -2.36% 3.26%
wpBeforeTemplate 22.6 ms +16.11% -2.3% 22.72 ms +14.88% -4.53% -0.53%
wpTemplate 17.12 ms +3.1% -3.27% 17.29 ms +3.82% -8.73% -0.98%
wpTotal 39.73 ms +13.31% -2.14% 39.78 ms +11.84% -5.46% -0.13%
wpMemoryUsage 7.72 MB +0% -0% 7.68 MB +0% -0% 0.43%
wpDbQueries 16 +0% -0% 16 +0% -0% 0%

front-end-classic-theme

Metric 29df945 trunk % Change
timeToFirstByte 35.3 ms +4.39% -1.98% 35.7 ms +5.04% -3.08% -1.12%
largestContentfulPaint 80 ms +2.5% -5% 80 ms +0% -5% 0%
lcpMinusTtfb 44.1 ms +2.95% -4.08% 42.95 ms +3.49% -3.26% 2.68%
wpBeforeTemplate 19.27 ms +2.7% -0.47% 19.61 ms +2.5% -2.09% -1.73%
wpTemplate 13.06 ms +5.44% -3.68% 13.17 ms +2.96% -3.19% -0.84%
wpTotal 32.49 ms +4.74% -1.72% 32.98 ms +5.4% -2.91% -1.49%
wpMemoryUsage 6.41 MB +0% -0% 6.37 MB +0% -0% 0.53%
wpDbQueries 13 +0% -0% 13 +0% -0% 0%

media-processing

Metric 29df945 trunk % Change
mediaProcessingJpeg 325.62 ms +6.67% -0.72% 328.92 ms +0.19% -0.14% -1%
mediaProcessingAvif 4863.79 ms +0.41% -0.24% 4873.05 ms +0.46% -0.16% -0.19%
mediaProcessingJpegToAvif 3386.21 ms +1.63% -0.47% 3406.57 ms +0.53% -0.29% -0.6%

media-upload

Metric 29df945 trunk % Change
jpegUploadProcessing 1431.71 ms +2.37% -1.01% 1434.31 ms +0.93% -0.86% -0.18%
pngUploadProcessing 220.51 ms +4.97% -2.52% 222.34 ms +39.2% -7.16% -0.82%
largeJpegUploadProcessing 1418.64 ms +1.69% -0.29% 1414.72 ms +0.82% -0.31% 0.28%
multipleImageUploadProcessing 1489.5 ms +0.82% -0.1% 1497.76 ms +0.3% -0.37% -0.55%

post-editor

Metric 29df945 trunk % Change
serverResponse 307.45 ms +5.1% -6.78% 318.71 ms +0.46% -8.99% -3.53%
firstPaint 390.18 ms +2.01% -14.27% 275.57 ms +37.93% -8.15% 41.59%
domContentLoaded 674.79 ms +4.92% -2.04% 661.26 ms +2.37% -1.81% 2.05%
loaded 675.46 ms +4.94% -2.03% 661.94 ms +2.36% -1.8% 2.04%
firstContentfulPaint 403.64 ms +7.89% -3.14% 388.78 ms +2.47% -2.11% 3.82%
firstBlock 1683.85 ms +8.75% -0.63% 1672.97 ms +0.35% -1.58% 0.65%
type 14.35 ms +2.44% -7.11% 13.45 ms +5.43% -7.81% 6.69%
typeWithoutInspector 14.19 ms +2.26% -8.17% 13.67 ms +3% -10.46% 3.8%
typeWithTopToolbar 17.7 ms +4.35% -3.73% 19.41 ms +0.98% -11.59% -8.81%
typeContainer 6.82 ms +7.18% -11% 6.7 ms +9.55% -13.58% 1.79%
focus 89.84 ms +6.02% -2.07% 91.84 ms +1.93% -3.51% -2.18%
firstFocus 193.18 ms +0% -0% 186.76 ms +0% -0% 3.44%
selectAll 300.33 ms +0.16% -2.11% 297.05 ms +1.48% -0.08% 1.1%
undo 24.46 ms +2.62% -3.72% 24.02 ms +7.29% -4.29% 1.83%
listViewOpen 60.08 ms +6.81% -7.19% 57.33 ms +1.31% -11.51% 4.8%
inserterOpen 31.88 ms +3.73% -4.27% 32.57 ms +7.25% -8.11% -2.12%
inserterHover 9.05 ms +7.85% -9.94% 8.79 ms +5.46% -7.51% 2.96%
inserterSearch 6.8 ms +8.09% -2.06% 6.61 ms +8.62% -0.61% 2.87%
loadPatterns 493.44 ms +2.65% -2.53% 490.46 ms +1.25% -1.76% 0.61%
wpTotal 298.92 ms +5.2% -6.99% 310.07 ms +0.53% -9.31% -3.6%
wpMemoryUsage 14.76 MB +0% -0% 14.73 MB +0% -0% 0.24%
wpDbQueries 55 +0% -0% 55 +0% -0% 0%

site-editor

Metric 29df945 trunk % Change
serverResponse 445 ms +8.02% -5.03% 459.94 ms +2.18% -0.64% -3.25%
firstPaint 369.32 ms +2.3% -7.55% 358.66 ms +3.64% -6.33% 2.97%
domContentLoaded 856.5 ms +2.9% -1.32% 838.19 ms +2.19% -0.7% 2.18%
loaded 857.51 ms +2.93% -1.32% 839.24 ms +2.18% -0.7% 2.18%
firstContentfulPaint 494.77 ms +2.54% -1.23% 494.07 ms +1.31% -1.19% 0.14%
firstBlock 2522.97 ms +3.17% -0.73% 2493.34 ms +1.12% -1.44% 1.19%
type 17.05 ms +7.68% -6.39% 16.21 ms +4.87% -5.18% 5.18%
navigate 117.06 ms +4.97% -7.27% 110.4 ms +5.47% -3.21% 6.03%
loadPatterns 1218.64 ms +6.48% -9.99% 1295.07 ms +13.19% -15.83% -5.9%
loadPages 952.21 ms +4.02% -1.43% 966.89 ms +2.91% -2.5% -1.52%
wpTotal 435.51 ms +8.24% -5.12% 450.44 ms +2.2% -0.65% -3.31%
wpMemoryUsage 12.78 MB +0% -0% 12.75 MB +0% -0% 0.27%
wpDbQueries 45 +0% -0% 45 +0% -0% 0%

be58dba Run

🏁 Flaky tests

Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

Page List converts to Navigation Links with entity bindings in /test/e2e/specs/editor/blocks/navigation.spec.js, passed after 1 failed attempt.
Error: expect(locator).toContainText(expected) failed

Locator: getByRole('region', { name: 'Editor settings' }).getByRole('tabpanel', { name: 'Content' }).getByRole('button', { name: /Link to:/ })
Expected substring: "test-page-1"
Received string:    "Link to:Cat/catPagePublished"
Timeout: 5000ms

Call log:
  - Expect "toContainText" getByRole('region', { name: 'Editor settings' }).getByRole('tabpanel', { name: 'Content' }).getByRole('button', { name: /Link to:/ }) with timeout 5000ms
  - waiting for getByRole('region', { name: 'Editor settings' }).getByRole('tabpanel', { name: 'Content' }).getByRole('button', { name: /Link to:/ })
    14 × locator resolved to <button type="button" aria-expanded="false" aria-haspopup="dialog" class="components-button link-preview-button is-next-40px-default-size is-secondary">…</button>
       - unexpected value "Link to:Cat/catPagePublished"

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:1949:31
Undo restores the post selection when another synced entity is loaded (RTC WebSocket) in /test/e2e/specs/editor/collaboration/collaboration-undo-redo.spec.ts, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 2
+ Received  + 2

  Object {
    "attributeKey": "content",
    "blockIndex": 0,
    "content": "abcdef",
-   "endOffset": 3,
-   "offset": 3,
+   "endOffset": 2,
+   "offset": 2,
  }

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/collaboration/collaboration-undo-redo.spec.ts:363:5
inserts a block should show a blue line indicator in /test/e2e/specs/editor/various/inserting-blocks.spec.js, passed after 1 failed attempt.
TimeoutError: locator.boundingBox: Timeout 10000ms exceeded.
Call log:
  - waiting for locator('data-testid=block-list-insertion-point-indicator')

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/inserting-blocks.spec.js:678:41

be58dba Run

@im3dabasia

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@github-actions github-actions Bot added the [Package] Editor /packages/editor label Oct 21, 2026
@coderabbitai

coderabbitai Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

@im3dabasia, I’ll review the PR changes.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository: WordPress/gutenberg/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: a8d00268-67cb-496b-8c8f-5ffc2fa36028
📥 Commits

Reviewing files that changed from the base of the PR and between b9b5975 and 7ae963b.

📒 Files selected for processing: 11
  • packages/editor/CHANGELOG.md
  • packages/editor/src/components/post-revisions-preview/revisions-code-diff.jsx
  • packages/editor/src/components/post-revisions-preview/style.scss
  • packages/editor/src/components/post-revisions-preview/test/revisions-code-diff.jsdom.test.jsx
  • packages/editor/src/components/styles-canvas/revision-details.tsx
  • packages/editor/src/components/styles-canvas/revisions-code-diff.tsx
  • packages/editor/src/components/styles-canvas/revisions.jsx
  • packages/editor/src/components/styles-canvas/style.scss
  • packages/editor/src/components/styles-canvas/test/revision-details.jsdom.test.tsx
  • packages/editor/src/components/styles-canvas/test/revisions-code-diff.jsdom.test.tsx
  • test/e2e/specs/site-editor/user-global-styles-revisions.spec.js

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

📝 Summary

Summary by CodeRabbit

  • New Features

    • Compare global styles revisions with the current version side by side.
    • Switch between visual previews and formatted styles/settings code diffs.
    • View clear labels, line changes, current-version indicators, authors, and revision dates.
    • Responsive layouts stack visual previews on smaller screens.
    • Added messages for matching styles, missing selections, and unavailable comparison data.
  • Bug Fixes

    • Improved handling of unequal, empty, or invalid revision comparisons.

The revisions canvas now supports visual and code comparisons between a selected global styles revision and current styles. It displays revision details and renders selected and current previews side by side when they differ.

Changes: Global styles revision comparison

Layer / File(s) Summary
Shared split-diff rendering
packages/editor/src/components/post-revisions-preview/revisions-code-diff.jsx, packages/editor/src/components/post-revisions-preview/style.scss, packages/editor/src/components/post-revisions-preview/test/revisions-code-diff.jsdom.test.jsx
Shared diff logic generates paired previous and current rows. New split tables display both sides with line numbers, change markers, accessible labels, and empty cells. Styles and tests cover the split layout and row pairing.
Revision details and styles comparison
packages/editor/src/components/styles-canvas/revision-details.tsx, packages/editor/src/components/styles-canvas/revisions-code-diff.tsx, packages/editor/src/components/styles-canvas/test/*
Revision details show localized labels, dates, and available author information. Styles comparison serializes settings and styles with sorted object keys, then renders a split diff when configurations differ. Tests cover metadata exclusion, serialization, labels, and comparison states.
Revision canvas views and layout
packages/editor/src/components/styles-canvas/revisions.jsx, packages/editor/src/components/styles-canvas/style.scss, packages/editor/CHANGELOG.md, test/e2e/specs/site-editor/user-global-styles-revisions.spec.js
The canvas adds visual and code views, revision headers, and conditional selected/current previews. Responsive styles arrange the comparison panes. End-to-end tests cover differing and matching revisions and view switching. The changelog documents the comparison feature.

Priority: Normal

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant Editor
  participant RevisionsCanvas
  participant StylesRevisionsCodeDiff
  participant SplitCodeDiffTable
  participant RevisionPreview
  Editor->>RevisionsCanvas: Provide selected revision and current styles
  RevisionsCanvas->>StylesRevisionsCodeDiff: Request comparison in code view
  StylesRevisionsCodeDiff->>SplitCodeDiffTable: Render paired diff rows
  RevisionsCanvas->>RevisionPreview: Render selected and current previews in visual comparison
Loading

Suggested reviewers: ciampo

Merge Risk: Minimal · up to 7ae96

The checked comparison paths preserve the intended behavior. No merge-blocking issue was established.

Pre-merge checks: Passed 4
Check name Status Explanation
Title check Passed The title clearly and concisely describes the primary change: comparing a selected style revision with the current version side by side.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Description check Passed The pull request description clearly explains the style revision comparison feature, including visual and code views, responsive behavior, implementation details, and testing. It directly matches the …
Full details: Description check

Explanation

The pull request description clearly explains the style revision comparison feature, including visual and code views, responsive behavior, implementation details, and testing. It directly matches the changeset.

✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@im3dabasia

Copy link
Copy Markdown
Contributor Author

cc @ramonjd, since this builds on your side-by-side proof of concept. Still in draft pending the design questions above; I'll request review once those are settled.

@im3dabasia

Copy link
Copy Markdown
Contributor Author

@jasmussen @mattmiklic could you take a look at the design when you get a chance? It adds the side-by-side comparison for Style revisions from #53484.

I have added the screencasts in the description. I'll open it for code review once the design is settled.

@im3dabasia
im3dabasia marked this pull request as ready for review October 27, 2026 04:56
@im3dabasia im3dabasia added the Needs Design Feedback Needs general design feedback. label Oct 27, 2026
@im3dabasia
im3dabasia requested a review from a team October 27, 2026 04:59
@jasmussen

Copy link
Copy Markdown
Contributor

Hey, thanks for the ping. At a glance on the videos, this looks like it's an improvement and working in the right direction, thanks for contributing.

However I'm missing a beat in testing this, I'm not seeing the side by side. What am I doing wrong?

state

@im3dabasia

Copy link
Copy Markdown
Contributor Author

However I'm missing a beat in testing this, I'm not seeing the side by side. What am I doing wrong?

Thanks for testing! Easy to mix up, but this one is for Style revisions, not page revisions.

Go to Site Editor → Styles → Revisions, then pick an older revision, and you'll see the side-by-side comparison.

You'll need at least two saved style changes first.

@jasmussen

Copy link
Copy Markdown
Contributor

Oh yeah, thanks, long week. Retesting:

state

Good progress! Not for this PR, but it would be nice to explore bringing over some of the red/yellow/green colour coding for what changed, like we have in page revisions.

One thing for this PR, though: both of the two PRs scroll independently. It seems like most diffint tools either keep the scrollbars in sync, so both scroll the same amount, or both "pages" are placed in the same scrollable container so there's only a single scrollbar. The point is to more easily compare before and after. Is that something we could make work here?

Thanks again for contributing!

@im3dabasia

Copy link
Copy Markdown
Contributor Author

thanks, @jasmussen! I agree that scrolling should be synchronized across both screens to make comparisons easier.

Here's a video reference for the proposed change, let me know what you think. feedbacks welcome!

Screen.Recording.2026-10-29.at.11.16.52.AM.mov

@jasmussen

Copy link
Copy Markdown
Contributor

Looks good to me. Absent any other feedback we receive, probably this can move into the code review portion. E.g. right now it's two scrollbars in sync, if for some reason that's complex, can it be one canvas with two page instances, very very tall, and then a single scrollbar? I have no strong opinion, only offering what-ifs.

@im3dabasia
im3dabasia requested a review from ellatrix October 29, 2026 10:14
@im3dabasia

Copy link
Copy Markdown
Contributor Author

Looks good to me. Absent any other feedback we receive, probably this can move into the code review portion. E.g. right now it's two scrollbars in sync, if for some reason that's complex, can it be one canvas with two page instances, very very tall, and then a single scrollbar? I have no strong opinion, only offering what-ifs.

Thanks, @jasmussen!

@ellatrix, would you mind taking a look when you get a chance?

@im3dabasia im3dabasia removed the Needs Design Feedback Needs general design feedback. label Nov 2, 2026
@im3dabasia
im3dabasia requested a review from ramonjd November 2, 2026 09:01

@ramonjd ramonjd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took this for a spin, this is great UX change, thanks for carrying the idea forward. Comparing visual changes by default makes sense for global styles, and the option to see the theme.json values would be valuable for theme devs.

I tested with some pretty crazy padding (2000px) and the scroll sync holds.

If there are no blockers I think we could get it in front of users.

I would like a second opinion though! cc @tellthemachines for confidence check

@tellthemachines

Copy link
Copy Markdown
Contributor

I would like a second opinion though! cc @tellthemachines for confidence check

Was there anything specific you wanted me to look at? From a quick test run it seems to be working pretty well, and it's a nice improvement.

It's a shame we don't have access to style revisions from the left hand side styles sidebar! But that's definitely something for another time :)

@ramonjd

ramonjd commented Nov 5, 2026

Copy link
Copy Markdown
Member

Was there anything specific you wanted me to look at? From a quick test run it seems to be working pretty well, and it's a nice improvement.

Not really, just a confidence check. 🙇🏻 I guess also any UX or a11y things that stand out to you.

I think once the userConfig bug is fixed we can ship it in that case.

Thanks for checking it out!!

@im3dabasia

Copy link
Copy Markdown
Contributor Author

Thanks both! @ramonjd, both of your comments are addressed. Mind another look? @tellthemachines, I'll open a follow-up issue for the sidebar entry point.

@ramonjd
ramonjd force-pushed the add/style-revisions-code-diff branch from 6c4c429 to be58dba Compare November 6, 2026 05:00

@ramonjd ramonjd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just gave this PR a rebase. Thanks for the efforts on this feature.

@im3dabasia

Copy link
Copy Markdown
Contributor Author

Thank you to everyone who contributed to this PR. I really appreciate all the effort that went into getting this shipped!

As @tellthemachines suggested, the Site Editor should have a Revisions button in the left-hand sidebar, allowing users to quickly check revisions without having to leave the editor. I've opened a follow-up PR to address this: #86411

This is already available in the V2 Site Editor, so we're not introducing anything new here; we're simply bringing the same functionality to V1 as well. IMO, this is a valuable addition.

Thanks again to everyone who was involved in the review process for this PR. I would really appreciate your feedback and inputs on the follow-up PR (#86411) as well.

Thanks, everyone!

@im3dabasia
im3dabasia merged commit 1792dc9 into trunk Nov 6, 2026
95 of 98 checks passed
@im3dabasia
im3dabasia deleted the add/style-revisions-code-diff branch November 6, 2026 06:08
@github-actions github-actions Bot added this to the Gutenberg 24.5 milestone Nov 6, 2026
@paulopmt1 paulopmt1 added [Type] Feature New feature to highlight in changelogs. and removed [Type] Enhancement A suggestion for improvement. labels Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Feature] History History, undo, redo, revisions, autosave. [Package] Editor /packages/editor [Type] Feature New feature to highlight in changelogs.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants