Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-68314

Line break after code block macros are ignored in the old editor

      Issue Summary

      When using the old editor, line breaks after code block macros are ignored. In the storage format, you can see this

      <p class="auto-cursor-target"><br /><br />&nbsp;&nbsp;</p>
      

      Steps to Reproduce

      1. Add a text
      2. Add a code macro
      3. Add a few line break right after the code macro
      4. Add a text

      Screencast:

      Expected Results

      Line breaks

      Actual Results

      Line breaks are ignored in the published mode but visible in the editor

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [CONFCLOUD-68314] Line break after code block macros are ignored in the old editor

            Atlassian Update - October 26, 2021

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - October 26, 2021 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team!

            Trent Murray added a comment - - edited

            Given this will get ignored, there's a terrible workaround for anyone who experiences this which doesn't solve the issue, but makes it look less shit.

             

            Using a style macro, put some artificial 2em margins around the element. If you put this in your templates, you won't need to keep adding it to each page, but it really makes your pages in edit more look garbage and prone to problems.

             

            .auto-cursor-target { margin: 2em 0 2em 0; }
            

             

            Trent Murray added a comment - - edited Given this will get ignored, there's a terrible workaround for anyone who experiences this which doesn't solve the issue, but makes it look less shit.   Using a style macro, put some artificial 2em margins around the element. If you put this in your templates, you won't need to keep adding it to each page, but it really makes your pages in edit more look garbage and prone to problems.   .auto-cursor-target { margin: 2em 0 2em 0; }  

            Should I hold my breath on this one, or we looking at a few years?

            Trent Murray added a comment - Should I hold my breath on this one, or we looking at a few years?

              Unassigned Unassigned
              mariffin Mohamed Hazwan Ariffin (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: