Issue Summary

Confluence Cloud's version history comparison tool incorrectly flags unchanged images (including images nested inside Expand macros) as edits when comparing the latest version of a page against its previous version.

In testing, only a single word in an H1 heading was modified, yet the diff reported 18 changes, with the surplus attributed to unmodified images and image-containing macros. The AI-generated change summary, by contrast, correctly identifies only the real edit — confirming the underlying page data is intact and the defect lies in the diff engine's change-counting logic.

Notably, this issue is scoped to the most recent version comparison only — comparisons between older (non-latest) versions render correctly.

Steps to Reproduce

1. Create a new Confluence page.
2. Add 3 Expand macros, named TEST 1, TEST 2, TEST 3.
3. Inside TEST 1 — add text only (no image).
4. Inside TEST 2 — add an image.
5. Inside TEST 3 — add an image.
6. Save the page → Version 1.
7. Re-open the page and edit only the H1 heading (e.g. change one word: "Bug" → "Issue").
8. Save the page → Version 2.
9. Navigate to Page History (⋯ menu → Page History).
10. Select Compare between Version 1 and Version 2.

Expected Result

The version comparison displays 1 change — the single-word edit to the H1 heading. Unmodified images (including those inside Expand macros) do not appear in the diff.

Actual Result

The version comparison reports multiple changes (e.g. 18 changes when only 1 was made). The extra changes are incorrectly attributed to:

• Images inside Expand macros (TEST 2, TEST 3) — flagged as edits despite being unchanged.

• Expand macros containing only text (TEST 1) are not affected.

Workaround

There is currently no workaround that fully restores correct version comparison behaviour.