Confluence Cloud Version History Renders Tables as One Character Per Line

XMLWordPrintable

    • 1
    • Major

      Issue

      When viewing page version history in Confluence Cloud — both the single historical version view and the version comparison (diff) view — pages originally authored in the legacy TinyMCE editor that contain tables render with columns collapsed to approximately one character wide. Content appears stretched vertically with one letter per line, making version history completely unreadable.

      The live/current page renders correctly. Page content is not corrupted — this is purely a display defect in the version history rendering pipeline.

      Steps to Reproduce

      1. Open a Confluence Cloud page that was originally created in the legacy TinyMCE editor and contains tables (particularly with short cell content such as status labels, codes, or Insert Excerpt macro content).
      2. Click the (more actions) menu → select Page history.
      3. Click on any historical version number to view that version.
      4. Observe the table rendering in the version view.
      5. Alternatively, select two versions and click Compare to view the diff — observe the same rendering issue.

      Note: The page's storage format should use <ac:layout> tags and legacy XHTML table structures with zero, empty, or percentage-only <col> widths. This can be verified via Advanced detailsView Storage Format.

      Expected Result

      Version history displays page content with proper table column widths, matching or closely approximating the live page appearance. Tables should be readable with appropriate column sizing.

      Actual Result

      Table columns collapse to approximately 1 character width. Text renders vertically — one letter per line — making the entire version history page unreadable. This occurs in:

      • Single version view (via XHTML → ADF conversion path)
      • Version comparison/diff view (via DaisyDiff path)

      Both paths produce the same visual defect through different mechanisms. The issue is consistent and reproducible across all historical versions of affected pages.

      Workaround

      No viable workaround exists for viewing historical versions.
       

              Assignee:
              Unassigned
              Reporter:
              Tanya -
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: