-
Bug
-
Resolution: Timed out
-
Low
-
None
-
3
-
Severity 3 - Minor
-
Summary
Following a link from one page to an anchor on another page in Firefox will only bring you to the top of the linked page, and not directly to the anchor.
Environment
- Firefox 39.0
- Confluence 5.9.1
Steps to Reproduce
- Create a page in Confluence with anchor links on a few items.
- On a separate page, create a direct link to the anchor link. (i.e. https://CONFLUENCE_URL/display/SPACEKEY/PAGE_NAME#ANCHOR_LINK)
- Attempt to follow the anchor link in Firefox, either from the 2nd page, or directly via the address bar.
Expected Results
In Chrome and other browsers, clicking the link will take you directly to the anchor.
Actual Results
- Link will take you to the top of the linked page, but not directly to the anchor.
- Additionally, you can try following the link directly from your address bar. You'll have the same behavior.
Workaround
Use another browser, such as Chrome.
- is related to
-
-
- Closed
-
[CONFCLOUD-53926] Unable to follow anchor link to another page in Firefox
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: affects-cloud pages | New: affects-cloud pages stale-bulk-close202008 |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2364433 ] | New: JAC Bug Workflow v3 [ 3429429 ] |
| Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
| Link |
New:
This issue is related to |
| Support reference count | Original: 2 | New: 3 |
| Support reference count | Original: 1 | New: 2 |
Tom Dayton
added a comment - After more experimentation on my Mac, I've gotten linking to an anchor across pages to work in Safari (11.0 (12604.1.38.1.7) and Firefox (56.0), but not in Chrome (61.0.3163.100). It used to work in Chrome. After much angrifying experimentation with the multiple, conflicting instructions Atlassian provides, the URL format that currently works for Safari and Firefox is the one revealed by this procedure:
- Add text in front of the anchor you want to link to–on the same line.
- Make that line a header.
- Add a table of contents.
- Save the page.
- Click the Table of Contents entry for that line.
- In the the browser's nav entry field, you'll see at the end of the URL the anchor name. Concatenated to the anchor name is the header text. Delete that header text, leaving the anchor name.
- Copy the resulting URL. That URL will work in Safari and Firefox, but not in Chrome.
- Use that same procedure for every other page. Within a given page, you can simply replace the anchor name at the end of the URL. But each page has its own page ID, which you will need to replace.
Tom Dayton
added a comment - After more experimentation on my Mac, I've gotten linking to an anchor across pages to work in Safari (11.0 (12604.1.38.1.7) and Firefox (56.0), but not in Chrome (61.0.3163.100). It used to work in Chrome. After much angrifying experimentation with the multiple, conflicting instructions Atlassian provides, the URL format that currently works for Safari and Firefox is the one revealed by this procedure:
Add text in front of the anchor you want to link to–on the same line.
Make that line a header.
Add a table of contents.
Save the page.
Click the Table of Contents entry for that line.
In the the browser's nav entry field, you'll see at the end of the URL the anchor name. Concatenated to the anchor name is the header text. Delete that header text, leaving the anchor name.
Copy the resulting URL. That URL will work in Safari and Firefox, but not in Chrome.
Use that same procedure for every other page. Within a given page, you can simply replace the anchor name at the end of the URL. But each page has its own page ID, which you will need to replace.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!