Bug
Unable to link one ArcGIS Enterprise site to a section of another site using an HTML anchor tag and configured ID on a section.
| Bug ID Number | BUG-000172007 |
|---|---|
| Submitted | November 5, 2024 |
| Last Modified | July 2, 2025 |
| Applies to | Portal for ArcGIS |
| Version found | 11.1 |
| Operating System | N/A |
| Operating System Version | N/A |
| Status | Known Limit |
Additional Information
The root cause of the issue lies in how ArcGIS Enterprise Sites uses single-page application (SPA) routing, which interferes with standard HTML anchor behavior. In SPAs like ArcGIS Sites, the # symbol in the URL is not treated as a traditional anchor but is instead used for client-side navigation (routing between virtual pages). When you create a link such as: https://your-domain.com/portal/apps/sites/#/site2/#explore-topic The browser treats everything after the first # as part of the SPA route, meaning the #explore-topic portion is never interpreted by the browser as an instruction to scroll to an element with that ID. Instead, the ArcGIS app receives /site2/#explore-topic as a single routing string, and since ArcGIS Sites does not parse or act on that second fragment, no scrolling occurs. To illustrate: in standard HTML, a link like https://example.com/page#section1 would scroll to. But in ArcGIS Sites, a link like #/site2/#section1 just routes to the site, and the browser ignores the #section1 part—because it’s already using the first # for app-level routing. This makes direct anchor links across different sites or pages within the ArcGIS Sites environment ineffective without custom scripting or alternate workarounds.
Steps to Reproduce
Bug ID: BUG-000172007
Software:
- Portal for ArcGIS
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App