Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-45182

Vertical spacing removed on preview or publish after certain user operations

    NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

    Summary

    Using some operations are causing vertical spacing between the macros to be stripped out as auto-cursor-target class is applied.

    Steps to Reproduce

    Steps to reproduce:

    1. Start creating a newpage
    2. Insert a block macro (e.g. the info macro)
    3. Insert another macro below the first (e.g. another info macro)
    4. In the space between the two macros, add a line break (in the editor DOM there are now two paragraphs between the macros - one with the auto-cursor-target class and one without)
    5. Click on preview and observe that there is vertical spacing between the macros
    6. Perform one of the "user operations" listed below - do this below the two macros to make the effect clearer to observe (in the editor DOM, both paragraphs between the macros now have the auto-cursor-target class applied)
    7. Click on preview and observe that the vertical spacing between the macros has been stripped out

    User operations known to cause this issue:

    • Wiki autoformatting (e.g. when you type h2. followed by a space to trigger heading formatting)
    • Cutting content (e.g. via cmd + v shortcut)

    This issue is only reproducible on instances that do not have the collaborative editing feature enabled.

    Expected Results

    The spaces are not modified

    Actual Results

    Vertical spacing between the macros were stripped out.

    Workaround

    Use operations on the top menu when available, such as selecting a text and making it title, instead of using h2..

          [CONFSERVER-45182] Vertical spacing removed on preview or publish after certain user operations

          Thank you for your response.

          I haven't been doing much with the wiki just recently, so I imagine it's fine.

          I suppose the part that confused me was that the 1000. versions started appearing long ago, but the version shown by "About Confluence" never changed.  I suppose I imagined there would be announcement when the fix was actually pushed to the Cloud, but now I see that's not the case.

           

          Patrick Turley added a comment - Thank you for your response. I haven't been doing much with the wiki just recently, so I imagine it's fine. I suppose the part that confused me was that the 1000. versions started appearing long ago, but the version shown by "About Confluence" never changed.  I suppose I imagined there would be announcement when the fix was actually pushed to the Cloud, but now I see that's not the case.  

          Hi pturley, the fix versions prefixed with 1000. on this ticket indicate the first Confluence Cloud version with the fix in place. All Confluence Cloud instances should have had this fix for a couple of weeks now.

          If you're still seeing unexpected vertical spacing behaviour on your Cloud instance, could you please reach out to our support team so that we can investigate further?

          edith (Inactive) added a comment - Hi pturley , the fix versions prefixed with 1000. on this ticket indicate the first Confluence Cloud version with the fix in place. All Confluence Cloud instances should have had this fix for a couple of weeks now. If you're still seeing unexpected vertical spacing behaviour on your Cloud instance, could you please reach out to our support team so that we can investigate further?

          @Jade,

          Can you estimate when this will be available for Confluence Cloud (is that the proper name)?

          Patrick Turley added a comment - @Jade, Can you estimate when this will be available for Confluence Cloud (is that the proper name)?

          A fix for this issue is now available for Confluence Server customers.
          Upgrade now or check out the Release Notes to see what other issues are resolved.

          Jade Giacoppo (Inactive) added a comment - A fix for this issue is now available for Confluence Server customers. Upgrade now or check out the Release Notes to see what other issues are resolved.

          Patrick Turley added a comment - - edited

          Please see JST-239435 for evidence that the "fix" may have broken the table of contents.

          Patrick Turley added a comment - - edited Please see JST-239435 for evidence that the "fix" may have broken the table of contents.

          FYI, the workaround described above doesn't help the problem.  You should delete it.

          Patrick Turley added a comment - FYI, the workaround described above doesn't help the problem.  You should delete it.

          PLEASE release this already!

          I'm tired of using 7 blank lines where 2 used to be enough, and knowing that, once this is released, I'll have to go back in and delete most of the blank lines.

          Geez!

           

          Patrick Turley added a comment - PLEASE release this already! I'm tired of using 7 blank lines where 2 used to be enough, and knowing that, once this is released, I'll have to go back in and delete most of the blank lines. Geez!  

          Excellent. Thank you.

          Patrick Turley added a comment - Excellent. Thank you.

          Hi pturley, clicking on Help > About Confluence from the Confluence header should open a dialog with the version information for your instance:

          edith (Inactive) added a comment - Hi pturley , clicking on Help > About Confluence from the Confluence header should open a dialog with the version information for your instance:

          How can I tell what version of Confluence my Cloud instance is running? It's not obvious.

          Patrick Turley added a comment - How can I tell what version of Confluence my Cloud instance is running? It's not obvious.

            wiwong wilson
            etom edith (Inactive)
            Affected customers:
            1 This affects my team
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: