Summary

      When a Confluence user creates a page with Anchor links on them, upon clicking the links it doesn't take the user to the accurate position where the Anchor was placed.

      Environment

      This issue was reproduced on Confluence 6.6.8 but can affect other versions.

      Steps to Reproduce

      Scenario 1

      • Create a page with Anchors and links pointing to the Anchor.
      • Validate if the links are pointing to the right section of the page where Anchors are specified.
      • Once the page is created/saved resize the Confluence UI to a smaller dimension.

      Actual Results

      Upon clicking the link when the browser is resized to a smaller dimension, it doesn't take us to the right section as the header of the page seems to be blocking the Anchor location.

      Expected Results

      Links point to the right section on the page

      Scenario 2

      • Create a page with Anchors and links pointing to the Anchor.
      • Place the Anchor at the top and link in the middle of the page
      • Validate if the links are pointing to the right section of the page where Anchors are specified.

      Actual Results

      Upon clicking the link, it doesn't take us to the right section as the header of the page seems to be blocking the Anchor location.

      Expected Results

      Links point to the right section on the page

      Workaround

      N/A

            [CONFSERVER-57767] Anchor Links doesn't work as expected

            I am using Confluence 7.4.11 and this bug is present. Is version 7.8.0 released? If so, I will poke my administrator to upgrade. This bug has bothered me and zillions of others for many years.

            rolland.vandersluis added a comment - I am using Confluence 7.4.11 and this bug is present. Is version 7.8.0 released? If so, I will poke my administrator to upgrade. This bug has bothered me and zillions of others for many years.

            Tam Tran added a comment -

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

            Tam Tran added a comment - A fix for this issue is available to Server and Data Center customers in Confluence 7.8.0 Upgrade now or check out the Release Notes to see what other issues are resolved.

            Radek Janata added a comment - - edited

            We were experiencing a similar issue - a link to a heading (h1, h2, ...) was always positioned approx. 50px below and the main heading was covered by the Edit header/strip. We were able to workaround this in Confluence's Stylesheet using the custom CSS below.

            h1[id]:not(.with-breadcrumbs)::before,  
            h2[id]:not(.with-breadcrumbs)::before,  
            h3[id]:not(.with-breadcrumbs)::before,  
            h4[id]:not(.with-breadcrumbs)::before,  
            h5[id]:not(.with-breadcrumbs)::before,  
            h6[id]:not(.with-breadcrumbs)::before {  
              content: "";  
              display: block;  
              height: 50px;  
              margin: -50px 0 0;  
            } 
            

            Source: https://stackoverflow.com/questions/4086107/fixed-page-header-overlaps-in-page-anchors (the solution using :target::before didn't work for us).

            Radek Janata added a comment - - edited We were experiencing a similar issue - a link to a heading (h1, h2, ...) was always positioned approx. 50px below and the main heading was covered by the Edit header/strip. We were able to workaround this in Confluence's Stylesheet using the custom CSS below. h1[id] :not (.with-breadcrumbs) ::before , h2[id] :not (.with-breadcrumbs) ::before , h3[id] :not (.with-breadcrumbs) ::before , h4[id] :not (.with-breadcrumbs) ::before , h5[id] :not (.with-breadcrumbs) ::before , h6[id] :not (.with-breadcrumbs) ::before { content : ""; display : block; height : 50px; margin : -50px 0 0; } Source: https://stackoverflow.com/questions/4086107/fixed-page-header-overlaps-in-page-anchors (the solution using :target::before didn't work for us).

              8c8bb50f2129 Ellen Oates
              cathikary Chandu
              Affected customers:
              15 This affects my team
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: