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

Enable Confluence body macros to accept the INLINE atlassian-macro-output-type.

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • 1
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      There was a change of behaviour from Confluence 4.3.7 to 5.3.4, in Confluence 4.3.7 our body macros used to accept the INLINE output type, however due to the CSS changes that option is no longer available.

      Find below the instructions on how reproduce this behaviour in our latest version, if you follow these same steps in 4.3.7 you will notice that the macro will be INLINE with the text.
      In my example I used a third party macro, however that behaviour will be the same with any of our bundled body macro.

      Steps to reproduce:

      1. Start a Confluence 5.3.4.
      2. Go to UPM and install "Confluence Source Editor".
      3. Download Reporting Plugin, can be either from marketplace or UPM.
        You will also need to get a free license for reporting plugin.
      4. Create a page.
      5. Use source editor and add below code:
        <ac:macro ac:name="report-link">
        <ac:parameter ac:name="atlassian-macro-output-type">INLINE</ac:parameter>
        <ac:default-parameter>content:url</ac:default-parameter>
        <ac:rich-text-body>
        <ac:emoticon ac:name="green-star"/>
        </ac:rich-text-body>
        </ac:macro> and some text here
        
      6. Once you hit save Confluence will change above code as following:
        <ac:structured-macro ac:name="report-link">
        <ac:parameter ac:name="atlassian-macro-output-type">INLINE</ac:parameter>
        <ac:parameter ac:name="">content:url</ac:parameter>
        <ac:rich-text-body>
        <ac:emoticon ac:name="green-star"/>
        </ac:rich-text-body>
        </ac:structured-macro>
        <p>and some text here</p>
        
      7. In below image you can see that "Some text" will be under the icon instead at the side:

      If you try to use the same code of step 5 in the source editor of Confluence 4.3.7, the code will not be changed and the image will be displayed as this:

      Workaround:

      If you edit the page using the UI you can put the "Some text" inside the Report Link block, however that text will be turned into a link:

      1. Editing the page:
      2. After saving:

      ps.: I've moved this case from a bug ticket to a feature request on a customers behalf.

        1. img1.PNG
          img1.PNG
          7 kB
        2. img2.PNG
          img2.PNG
          5 kB
        3. img4.PNG
          img4.PNG
          17 kB
        4. img5.PNG
          img5.PNG
          11 kB

            [CONFSERVER-31820] Enable Confluence body macros to accept the INLINE atlassian-macro-output-type.

            Thank you for raising this suggestion.
            We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
            For more context, check out our Community blog on our updated workflow for Suggestions
            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our updated workflow for Suggestions Cheers, Confluence Product Management

            Eric Dain added a comment -

            +1 for this feature!

            Eric Dain added a comment - +1 for this feature!

            We are on 5.9.5. No option for inline code block. Any plans or work-around for adding this?

            chip yglesia added a comment - We are on 5.9.5. No option for inline code block. Any plans or work-around for adding this?

            ES added a comment -

            Please consider as it is, i.e. a bug to correct

            ES added a comment - Please consider as it is, i.e. a bug to correct

            The report-link example described here is broken as described in Confluence 5.5.2 but appears to be fixed in Confluence 5.6.3. Other macros excerpt, htmlcomment, and tooltip can also be inlined again in Confluence 5.6.3.

            Wendy Fergusson added a comment - The report-link example described here is broken as described in Confluence 5.5.2 but appears to be fixed in Confluence 5.6.3. Other macros excerpt, htmlcomment, and tooltip can also be inlined again in Confluence 5.6.3.

            The fact that Confluence now puts everything onto a new line makes it much more difficult to use for technical documentation (according to your documentation a primary use case). Any plans to fix this?

            Felicity Chapman added a comment - The fact that Confluence now puts everything onto a new line makes it much more difficult to use for technical documentation (according to your documentation a primary use case). Any plans to fix this?

            Given the description ("There was a change of behaviour from Confluence 4.3.7 to 5.3.4, in Confluence 4.3.7 our body macros used to accept the INLINE output type, however due to the CSS changes that option is no longer available") it seems totally inappropriate to classify this as a feature request rather than a bug.

            Alistair Christie added a comment - Given the description ("There was a change of behaviour from Confluence 4.3.7 to 5.3.4, in Confluence 4.3.7 our body macros used to accept the INLINE output type, however due to the CSS changes that option is no longer available") it seems totally inappropriate to classify this as a feature request rather than a bug.

              Unassigned Unassigned
              dluvison Deividi Luvison (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: