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

Info / tip / warning / note (.aui-message) panels does not respect floating elements

      In previous versions of Confluence, when you floated a panel to the right of a page and put an info box in the page, the width of the panel respected the floated panel, and would not overlap with it. In newer versions of Confluence, only the contents of the info panel do - the border still overlaps with floating elements. I have attached a screenshot to indicate what I mean.

      STR:

      1. Create a page and in it put a panel at the top with loremipsum.
      2. Underneath put some loremipsum.
      3. Underneath that put an info panel and put some loremimpsum in that. Save the page.
      4. In the developer view of your browser, target the div for the first panel and assign it {float: right; width: 20%}

        . It will now float to the right of the page.

      Note that the loremipsum in the body of the page does not overlap with the panel, but the info box does. This is incorrect behaviour.

      EDIT
      Despite spending some time looking at it yesterday I have just figured out how to workaround it. You should set

      {overflow: auto}

      to .aui-message. This is a bit of a CSS hack, tbh, but it works.

        1. panelfloatfail.PNG
          90 kB
          Steve Goldberg

            [CONFSERVER-29465] Info / tip / warning / note (.aui-message) panels does not respect floating elements

            Thanks thogek for letting us know that this is still an issue. This was part of a bulk close; we looked at a sample of bugs related to the editor and noted that they were now obsolete due to newer features or had been fixed in an updated version of the editor. As mentioned, there was always a chance that not all issues had been resolved and we can reopen if the issue persists - please let me know what version of Confluence you are running. Thank you.

            Makisa Appleton added a comment - Thanks thogek  for letting us know that this is still an issue. This was part of a bulk close; we looked at a sample of bugs related to the editor and noted that they were now obsolete due to newer features or had been fixed in an updated version of the editor. As mentioned, there was always a chance that not all issues had been resolved and we can reopen if the issue persists - please let me know what version of Confluence you are running. Thank you.

            Tom Kiefer added a comment -

            ...we suspect that this issue is no longer relevant or was resolved...

            This suspicion is incorrect.
            The described buggy behavior still exhibits and is very frustrating.

            Did anyone actually validate this issue before closing it?

            Tom Kiefer added a comment - ...we suspect that this issue is no longer relevant or was resolved... This suspicion is incorrect. The described buggy behavior still exhibits and is very frustrating. Did anyone actually validate this issue before closing it?
            Makisa Appleton made changes -
            Resolution New: Obsolete [ 11 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Atlassian Update - September 2019

            Thank you for your interest in this ticket. The Confluence Server and Data Center team released a major upgrade to the editor in 6.14. Due to the age of this ticket and/or lack of updates, we suspect that this issue is no longer relevant or was resolved as a result of the upgrade and are now closing this ticket.

            If this issue is still a problem in your Confluence instance in version 6.15 or later, please tag me in your comment and we can reopen this ticket for review.

            You can read more about the editor upgrade in the 6.14 Release Notes.

            Thanks

            Makisa Appleton | Senior Product Manager, Confluence Server and Data Center

            Makisa Appleton added a comment - Atlassian Update - September 2019 Thank you for your interest in this ticket. The Confluence Server and Data Center team released a major upgrade to the editor in 6.14. Due to the age of this ticket and/or lack of updates, we suspect that this issue is no longer relevant or was resolved as a result of the upgrade and are now closing this ticket. If this issue is still a problem in your Confluence instance in version 6.15 or later, please tag me in your comment and we can reopen this ticket for review. You can read more about the editor upgrade in the 6.14 Release Notes . Thanks Makisa Appleton | Senior Product Manager, Confluence Server and Data Center
            Makisa Appleton made changes -
            Fix Version/s New: 6.14.0 [ 83892 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Bug Workflow v3 [ 2887428 ] New: CONFSERVER Bug Workflow v4 [ 2981153 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2795828 ] New: JAC Bug Workflow v3 [ 2887428 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow [ 2725855 ] New: JAC Bug Workflow v2 [ 2795828 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2400831 ] New: JAC Bug Workflow [ 2725855 ]
            Status Original: Open [ 1 ] New: Gathering Impact [ 12072 ]

              Unassigned Unassigned
              4c44925d5073 Steve Goldberg
              Affected customers:
              4 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: