SharePoint Document Issues

Fix SharePoint Back Button Processing Two Clicks in Document Libraries

Adam DavisAdam Davis Nov 3, 2026 869 views

Question details

Users experience a navigation issue in existing SharePoint document libraries where clicking the back button after viewing an image requires two clicks, unexpectedly returning them to the site home page.

Fix SharePoint Back Button Processing Two Clicks in Document Libraries
Product
Microsoft SharePoint
Device & OS
not provided
Scenario
Navigating back to the document library after previewing an image file.
Observed behavior
The first click on the back arrow appears to do nothing, while a second click processes both actions simultaneously, bypassing the document library and returning the user directly to the site home page.
Before you start

Verify if the issue occurs across multiple web browsers or in incognito mode, and check if it affects newly created document libraries to isolate the scope of the problem.

Solution 1Recommended

Escalate to Microsoft Support for Tenant-Level Investigation

Since this is a recognized configuration or backend bug affecting existing tenant document libraries, Microsoft escalation engineers need to collect logs to resolve it.

Forum support and standard troubleshooting cannot perform the tenant-level log collection required to fix this specific document library routing bug. Opening a formal support ticket is the most efficient path to a permanent resolution.

1
Access Microsoft 365 Admin Center

Navigate to the Microsoft 365 admin center and log in using your administrator credentials.

2
Create a New Service Request

Go to the 'Support' section in the left-hand navigation menu and click on 'New service request'.

3
Detail the Issue

Describe the double-click back button issue, specifying that it exclusively affects image previews in existing document libraries, while Word documents and new libraries function correctly.

4
Request Log Collection

Explicitly request that escalation engineers collect tenant-level logs or initiate a remote session to investigate the affected libraries.

Escalate to Microsoft Support for Tenant-Level Investigation
Admin Access Required: You must have Microsoft 365 administrator privileges to open a support ticket. If you are an end-user, contact your organization's IT department.
Free Microsoft Office alternative

Experience Seamless Document Management with WPS Office

Dealing with persistent cloud storage and web navigation bugs can disrupt your workflow. WPS Office provides a lightweight, highly compatible, and free alternative to Microsoft Office, ensuring smooth document viewing, editing, and management without interface glitches.

  1. 1. Download WPS Office: Visit the official WPS website and download the free desktop application for your operating system.
  2. 2. Install and Launch: Follow the simple installation prompts and launch the unified WPS Office suite.
  3. 3. Manage Files Seamlessly: Open your documents, spreadsheets, and presentations directly within the stable, tabbed workspace.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Built-in tabbed interface for seamless document switching and navigation.Lightweight desktop application offering a stable alternative to browser-based editing.Free to use with a familiar, user-friendly interface requiring zero learning curve.
microsoft office alternative - wps office

Frequently Asked Questions

Why does the back button only fail when previewing images in SharePoint?

This specific bug is tied to how SharePoint's image previewer (file viewer) interacts with the browser's history state in older or existing document library configurations, causing a mismatch in navigation steps.

Does this issue affect Word documents or videos in SharePoint document libraries?

No, user reports and testing indicate that previewing Word documents or videos in the same document library works correctly. The double-click back button bug is isolated strictly to image files.

Will clearing my browser cache fix the SharePoint back button issue?

No. Testing shows the problem persists across different browsers (Chrome, Edge, Firefox) and in incognito windows, indicating it is a backend library configuration issue rather than a local browser cache problem.