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

Include page macro doesn't respect image size from the included page

      Issue Summary

      When including a page within the new Confluence editor pictures which are included in the original page are displayed in their full size.

      Steps to Reproduce

      1. Create Page 1
      2. Add tables and images
      3. Publish page 1
      4. Create Page 2
      5. Add Include page macro to include Page 1
      6. Publish the page 2

      Expected Results

      • Pictures that are included in the original page are displayed in their full size.

      Actual Results

      • Include page macro should respect image size from the included page

      Workaround

            [CONFCLOUD-68983] Include page macro doesn't respect image size from the included page

            Hi everyone,

            This is ae40806d76ae from the Confluence team. This bug is fixed and I confirmed the functionality to be working as expected. 

            Sincerely,

            Dixon

            Dixon Cheng (Inactive) added a comment - Hi everyone, This is ae40806d76ae from the Confluence team. This bug is fixed and I confirmed the functionality to be working as expected.  Sincerely, Dixon

            Ethan Yew added a comment -

            Hi all, Ethan here from Atlassian's Editor team. Wanting to let you all know that this bug is on our radar to fix. Our focus is on the problem regarding image sizes. i.e. Images from another page being referenced in the include page macro are not being displayed in their full size, when the width of the original page has been set to full width.

            Unfortunately, we will have to extend the due date for resolving this bug to May of this year. We have uncovered some underlying architectural constraints which has renewed our understanding of the effort required to resolve this bug.

            In the meantime, some potential workarounds are listed below:

            • As mentioned by megan@atlassian.com you may also be able to use smart link embedded pages functionality (with the caveats mentioned)
            • As this bug only presents itself when referencing full width pages inside the Include page macro, I would suggest reverting the width of the source page being referenced to the default fixed-width mode instead if this is possible.  

            We appreciate your continued patience, and will continue to keep you updated on our progress in resolving this bug.

            Ethan

            Ethan Yew added a comment - Hi all, Ethan here from Atlassian's Editor team. Wanting to let you all know that this bug is on our radar to fix. Our focus is on the problem regarding image sizes. i.e. Images from another page being referenced in the include page macro are not being displayed in their full size, when the width of the original page has been set to full width . Unfortunately, we will have to extend the due date for resolving this bug to May of this year. We have uncovered some underlying architectural constraints which has renewed our understanding of the effort required to resolve this bug. In the meantime, some potential workarounds are listed below: As mentioned by megan@atlassian.com you may also be able to use smart link embedded pages functionality (with the caveats mentioned) As this bug only presents itself when referencing full width pages inside the Include page macro, I would suggest reverting the width of the source page being referenced to the default fixed-width mode instead if this is possible.   We appreciate your continued patience, and will continue to keep you updated on our progress in resolving this bug. Ethan

            ME (Inactive) added a comment - - edited

            A possible workaround is to use the link macro instead of the include page macro.

             

            The link macro has multiple options for how it should look: URL, inline, card, and embed.

             

            If you create a link to the page you want to include and choose the embed option for display, then you will see the entire contents of the page you're including.  Using this method, the images should scale the same as in the source (tested ok).

            Caveats:

            • The entire page is included: title, byline (author picture, date, etc)
            • This only works for fabric (new editor) pages, the link macro in the older TinyMCE editor doesn't have this capability.

             

            ME (Inactive) added a comment - - edited A possible workaround is to use the link macro instead of the include page macro.   The link macro has multiple options for how it should look: URL, inline, card, and embed.   If you create a link to the page you want to include and choose the embed option for display, then you will see the entire contents of the page you're including.  Using this method, the images should scale the same as in the source (tested ok). Caveats: The entire page is included: title, byline (author picture, date, etc) This only works for fabric (new editor) pages, the link macro in the older TinyMCE editor doesn't have this capability.  

            Len Quam added a comment -

            Confirming for Atlassian support that I'm still seeing images using the include page macro after a page refresh (and full browser cache clear).

            Len Quam added a comment - Confirming for Atlassian support that I'm still seeing images using the include page macro after a page refresh (and full browser cache clear).

            This shouldn't be low, it's important for displaying nested content properly.

            I have a workaround, if you float an image left inside a table and resize, it gets it up and running.

             

            I'd rather the image scale to the container it's in.

            David Hazelden added a comment - This shouldn't be low, it's important for displaying nested content properly. I have a workaround, if you float an image left inside a table and resize, it gets it up and running.   I'd rather the image scale to the container it's in.

            Any updates on that? Macro include shrinks images' sizes which makes them almost impossible to see the content.

            Bartosz Dopke added a comment - Any updates on that? Macro include shrinks images' sizes which makes them almost impossible to see the content.

            Dear Atlassian <3,

            After I registered a ticket this issue was made by you guys.

            I do not entirely agree with the content of the issue. The new editor seems to have a lot more issues when linking pages using the include page macro:

            1. When including a page within the new Confluence editor pictures which are included in the original page are displayed in their full size.

            2. Font size is also bigger than the original

            3. Table markup using color pallets is also not working. For instance:

            When including a page which has tables and colored cells, the colored cells are not included in the new included page.

            The include page macro is very important for us.

            Kianoesh Shademan added a comment - Dear Atlassian <3, After I registered a ticket this issue was made by you guys. I do not entirely agree with the content of the issue. The new editor seems to have a lot more issues when linking pages using the include page macro: 1. When including a page within the new Confluence editor pictures which are included in the original page are displayed in their full size. 2. Font size is also bigger than the original 3. Table markup using color pallets is also not working. For instance: When including a page which has tables and colored cells, the colored cells are not included in the new included page. The include page macro is very important for us.

            Font size is also bigger than the original

            Kianoesh Shademan added a comment - Font size is also bigger than the original

              b44ee328bea8 Ethan Yew
              jalor Janice Alor (Inactive)
              Affected customers:
              29 This affects my team
              Watchers:
              43 Start watching this issue

                Created:
                Updated:
                Resolved: