Impact of Google Chrome and Microsoft Edge XSLT Removal on Xerox DocuShare

Impact of Google Chrome and Microsoft Edge XSLT Removal on Xerox DocuShare

Browser vendors are removing native XSLT support. In DocuShare 8.0 and earlier, specific XForms pages rely on the browser's XSLT engine and may display raw XML, appear blank, or load without working controls after this browser change. DocuShare 8.1 resolves the issue by performing the transformation on the server and returning HTML to the browser.

Business Impact

If no action is taken, affected pages may render as raw XML, render blank, or fail to provide usable controls. Users may be unable to complete impacted administrative or action-driven workflows from Chrome or Edge.

This issue does not affect repository data integrity. The impact is limited to client-side rendering of specific pages.

Browser Timeline (Chrome/Chromium)

Edge is Chromium-based. Use the Chrome milestones above as the planning baseline unless Microsoft publishes a different schedule.

DocuShare Scope

If your site is running an affected DocuShare release, the following pages may display raw XML, appear blank, or load without working controls after Chrome or Edge stops running XSLT.

• Administration: Content Store Configuration, Content Intake Configuration and intake-rule editing, and Remote Connection Configuration and editing.
• Image Manager: the home page (Collection Explorer, Quick Search, Property Search, and Advanced Search) and the configuration page, including the Search Home Page, Document & Properties Viewer, and Document Types tabs.
• Everyday user actions: Rename and Edit for any object, Add Comments, and the Change History and Activity History pages.
• The Add page only when creating a wiki, wiki page, weblog, or weblog entry. Adding documents, collections, and other object types is unaffected.
• Wiki and weblog pages wherever they allow in-place editing, and custom forms attached to a content rule.
• Sites using the XForms-based login form. The standard DocuShare login page is not affected.

No repository content is at risk, and the rest of DocuShare continues to work normally. The Content Rule Manager, duplicate-rule page, Document Entry Template manager, and main administration console are not affected because these pages are generated on the server.

What Is Not Affected

• Core HTML-based interface pages for routine navigation, properties, upload, and download.
• Desktop and native clients that do not depend on a browser XSLT engine.
• Server-side operations such as indexing, workflow execution, scheduled jobs, and content rule execution.
• Server-to-server integrations over the DocuShare HTTP/XML API and WebDAV.

Resolution by Product Version

Interim Mitigation (Temporary)

For managed Chromium browsers, administrators can use the XSLTEnabled enterprise policy as a temporary bridge. This mitigation is time-limited and should be used only to support an upgrade plan, not as a long-term solution.

Custom Integration Qualification

If a custom solution uses XDBQuery with client-side stylesheet rendering in a browser, that page may fail after browser XSLT removal. Configure those requests to use server-side transformation by setting server_side_xsl=true.

Recommended Customer Action Plan

1. Inventory all DocuShare environments and identify the versions currently in use.

2. For environments running DocuShare 8.0 or earlier, plan and schedule an upgrade to DocuShare 8.1 whenever possible. If an upgrade cannot be completed now, install the specific patch identified in the resolution chart for your supported version.

3. Validate critical workflows in a browser build aligned to upcoming milestone behavior.

4. Review custom browser-based integrations that rely on client-side XSLT.

Support

For upgrade planning or release-specific guidance, contact Xerox DocuShare Support and reference this compatibility advisory.