• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 5.9.4, 5.9.14, 5.10.7, 6.0.7, 6.1.1, 6.2.1, 6.2.4, 6.6.7, 6.7.2, 6.9.1, 6.11.0
    • Content - Linking

      Summary

      Back button in browser does not return to previous page when using URL with anchor link

      Environment

      • Any browser
      • Confluence 6.2.1

      Steps to Reproduce

      1. Create Page A with content that scrolls beyond the bottom of the screen, with several headings in the content that also go below the fold
      2. Add a table of content macro at the top of Page A
      3. Create Page B and insert Web Links with anchors from the table of contents to point to headings on Page A after the fold, for example
      4. Save Page B
      5. Click on the link to go to Page A with the anchor
      6. Click the back button in the broswer

      Expected Results

      The browser goes back to page

      Actual Results

      You need to click twice to return to the previous page

      Notes

      The page rendering is completely different in newer versions of Confluence which is why this bug doesn't appear in older, EOL versions. The left hand nav and floating toolbar are new and are likely to be part of the issue here.

      Workaround

      The same workaround mentioned in CONFSERVER-40462 can be applied for this case (actions on Page A):

      1. Insert a new macro: Table of Content Zone
      2. Drag your original table of content macro icon into the new Table of Content Zone
      3. Click "Save"

       

            [CONFSERVER-52497] Back button in browser with anchor links behaves incorrectly

            I'm seeing what appears to be the same issue but from a somewhat different situation. We use a tool to generate HTML from some other content and then use the REST APIs to populate a page with that HTML. The generated HTML creates a TOC with <a href=#some-id> tags and then sets id=some-id attributes on other tags. (We had to jump through hoops to work around the id prefix manipulation done by Confluence, but we've worked out that issue.) The result is that clicking a link in the TOC jumps to the element with the corresponding id attribute, but the Back button doesn't return to the top. We haven't inspected the page source, but whatever Atlassian has done to interfere with the behavior of the Back button is infuriating.

            The notion here applies (though somewhat backhandedly).

            Rob Stewart added a comment - I'm seeing what appears to be the same issue but from a somewhat different situation. We use a tool to generate HTML from some other content and then use the REST APIs to populate a page with that HTML. The generated HTML creates a TOC with <a href=#some-id> tags and then sets id=some-id attributes on other tags. (We had to jump through hoops to work around the id prefix manipulation done by Confluence, but we've worked out that issue.) The result is that clicking a link in the TOC jumps to the element with the corresponding id attribute, but the Back button doesn't return to the top. We haven't inspected the page source, but whatever Atlassian has done to interfere with the behavior of the Back button is infuriating. The notion here applies (though somewhat backhandedly).

            Ben Hamilton added a comment - - edited

            My response to the updates we've not had? Lie down, try not to cry

            Ben Hamilton added a comment - - edited My response to the updates we've not had? Lie down, try not to cry

            Is there any update on this issue? We are facing it with 6.2.4

            Thanks.

            Laura Lesen added a comment - Is there any update on this issue? We are facing it with 6.2.4 Thanks.

            I wish I could (thumbs) the comments from Stephen Kairys. Honestly it is crying shame the that such a fundamental issue is left lying in the dirt for so long. Our client is VERY frustrated by this.

            My love for Atlassian is waning with it's inaction on this issue and it's recent changes to the UI which imho really don't improve the UX, it's harder to do simple stuff (Sidebar, page tree being two). 

            Not feeling the love.

            Ben Hamilton (EMS) added a comment - I wish I could (thumbs) the comments from Stephen Kairys. Honestly it is crying shame the that such a fundamental issue is left lying in the dirt for so long. Our client is VERY frustrated by this. My love for Atlassian is waning with it's inaction on this issue and it's recent changes to the UI which imho really don't improve the UX, it's harder to do simple stuff (Sidebar, page tree being two).  Not feeling the love.

            Stephen Kairys added a comment - - edited

            Update:

            I discovered something interesting. We have an old space at 5.5.2 which is going to be upgraded very soon. In the old version - which I realize is past "end of life", the bug does not exist. I copied the doc into our 6.3.2 test space and the bug is present.

            IMO, since this bug means that going to a higher version introduces issues for us (and I'm sure, others), it should be higher-priority to fix...since something obviously broke. It's impactful enough to discourage me from endorsing the upgrade to 6.3.2.

            And, it may force us to reorganize a document in a way that would make it less reader-friendly. Confluence is designed to facilitate communication with our audience, not hinder it.

            To be clear, the observed behavior is per an anchor link within same page. I did not investigate the behavior per linking to an anchor on another page.

            Thanks.

            Stephen Kairys added a comment - - edited Update: I discovered something interesting. We have an old space at 5.5.2 which is going to be upgraded very soon. In the old version - which I realize is past "end of life", the bug does not exist. I copied the doc into our 6.3.2 test space and the bug is present. IMO, since this bug means that going to a higher version introduces issues for us (and I'm sure, others), it should be higher-priority to fix...since something obviously broke. It's impactful enough to discourage me from endorsing the upgrade to 6.3.2. And, it may force us to reorganize a document in a way that would make it less reader-friendly. Confluence is designed to facilitate communication with our audience, not hinder it. To be clear, the observed behavior is per an anchor link within same page. I did not investigate the behavior per linking to an anchor on another page. Thanks.

            Stephen Kairys added a comment - - edited

            Hi,

            This bug came up and bit me when adding anchor links (within the same page) to a document. The behavior per hitting BACK was so unreliable that I removed some links. To put it another way, I sometimes hesitate to add an anchor link b/c of this reason. Both of the above hurt the quality and usability of our documents.

            This bug has now been on file for almost five months. Considering how it impacts basic browser functionality, I wish the priority could be upgraded from LOW to something higher. 

            PS: Please also see my screencast attachment under my comment from 15/Jun/2017 3:04 PM, which demonstrates the impact of this defect.

            Thanks.

            Stephen Kairys added a comment - - edited Hi, This bug came up and bit me when adding anchor links (within the same page) to a document. The behavior per hitting BACK was so unreliable that I removed some links. To put it another way, I sometimes hesitate to add an anchor link b/c of this reason. Both of the above hurt the quality and usability of our documents. This bug has now been on file for almost five months. Considering how it impacts basic browser functionality, I wish the priority could be upgraded from LOW to something higher.  PS: Please also see my screencast attachment under my comment from 15/Jun/2017 3:04 PM, which demonstrates the impact of this defect. Thanks.

            Additionally, if you're clicking on an anchor on the same page, clicking "back" will not take you to the previous location on the page.

            Robert Louie added a comment - Additionally, if you're clicking on an anchor on the same page, clicking "back" will not take you to the previous location on the page.

            Additionally, if you're clicking on an anchor on the same page, clicking "back" will not take you to the previous location on the page.

            Robert Louie added a comment - Additionally, if you're clicking on an anchor on the same page, clicking "back" will not take you to the previous location on the page.

            This is still a long standing issue for a client of ours.
            Can we expect an update on this bug in the near future?

             

            -Jared @ Evolution Marketing Services.

            Jared Dalrymple added a comment - This is still a long standing issue for a client of ours. Can we expect an update on this bug in the near future?   -Jared @ Evolution Marketing Services.

            Please see attached video per my prev. comment. Thank you.

            I'm running Chrome under WIn10.

            BACK button and EDIT mode.mp4

            Stephen Kairys added a comment - Please see attached video per my prev. comment. Thank you. I'm running Chrome under WIn10. BACK button and EDIT mode.mp4

              Unassigned Unassigned
              jrichards@atlassian.com James Richards
              Affected customers:
              12 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated: