Chrome drops XSLT: check your Acumatica Classic UI screens now

By DataForge team18 November 20264 min read

Chrome 158 turns off XSLT from 17 November, so unpatched Acumatica Classic UI screens can stop loading in Chrome and later in Edge.

What changed on 17 November

Google's published schedule set 17 November 2026 as the date Chrome 158 stops processing XSLT on the Stable channel. The only exceptions are sites in Google's origin trial and organisations using the XSLTEnabled enterprise policy. XSLT is an old way of turning XML data into a web page inside the browser. Google gives security as the reason for removing it. Browser XSLT depends on libxslt, an ageing C/C++ library with a history of memory-safety bugs, and Google puts XSLT usage at about 0.02% of page loads. Both exemptions stop working in Chrome 176 on 17 August 2027, and from then XSLT is off for every Chrome user.

Microsoft is about a month behind Google. A Microsoft 365 message centre notice published on 15 October says browser-native XSLT will be off by default from Edge 159 Stable, with rollout starting in mid-December 2026. The same notice says Microsoft plans to remove its temporary XSLTEnabled policy in Edge 176, targeted for mid-2027. Mozilla posted an intent to unship on 27 August that plans to disable XSLT in every Firefox channel in August 2027, in step with Chrome's final cutoff.

Why Acumatica customers feel the change first

Most staff won't notice anything when browser XSLT disappears. The exceptions are business systems whose older screens still rely on XSLT to draw the page, and Acumatica's Classic UI is the most relevant example for NZ firms because MYOB sells the platform here as MYOB Acumatica. Acumatica's community notice warns that without a fix, Classic UI screens won't load in Chrome or Edge. Companies that use a mix of Modern and Classic screens would see some workflows fail while others keep working. The Modern UI isn't affected.

A July patch may not be enough. Acumatica shipped its first fix for 2025 R1 and later in July, and its product team confirmed the fix went into 2025 R2 SP1, build 25.201.0213.5, released on 3 July. On 1 October Acumatica updated the notice to say an unexpected Chromium change had altered how XSLT behaved ahead of the planned removal. Acumatica said the July fix no longer covered the problem and scheduled expedited patches for 6 October (2026 R1) and 8 October (2025 R1 and 2025 R2). In the same thread, customers on 2025 R1 reported Classic screens failing in late September even after applying the earlier patch. SaaS customers get Acumatica's patches automatically, while private cloud (PCS) customers have to apply them manually. Versions 2024 R2 and earlier won't get a fix, so the only options there are an upgrade or a switch to Firefox.

MYOB Acumatica has its own version numbering. Avanza Solutions, an NZ MYOB Acumatica partner, says the XSLT problem is resolved in 2025.2.3 or higher, a build it expected in June 2026. That build predates Acumatica's October rework. Which MYOB build carries the October patches hasn't been published, so MYOB Acumatica customers should get the answer from their partner in writing.

A second deadline sits inside your next upgrade

Acumatica also announced on its news and updates page that the 2026 R2 release deprecates Classic UI. Customers upgrading to 2026 R2 can't turn the Modern UI off. Earlier versions keep Classic UI under Acumatica's standard support policy. AISI Dev's analysis treats the browser cutoff and the 2026 R2 removal as two separate deadlines, and NZ customers should plan for both. Any customised entry form, report or partner add-on that only opens in Classic UI needs a Modern UI version before the business moves to 2026 R2.

Firefox and the XSLTEnabled policy only buy time. Under Mozilla's plan, Firefox drops XSLT in August 2027. Chrome's enterprise policy stops working in the same month, and Edge's policy is due to go around then. A business that relies on either workaround has about nine months to finish its Modern UI work.

The wider exposure for NZ businesses

Acumatica isn't the only business software that relies on browser XSLT. The Access Group told customers of its Mosaic case management product that forms show a blank screen without browser XSLT, and it moved customers to a release without that dependency. Other places to look are older reporting portals, admin pages on network or factory equipment, and intranet tools built in-house years ago. Google's guidance points administrators to the Legacy Technology Report in the Chrome Enterprise console. Microsoft recommends running a Lighthouse audit in Edge DevTools and searching the results for XSLT warnings.

For a mid-sized NZ business, the likely failure is quiet. An accounts payable clerk or warehouse supervisor opens a familiar screen, sees a blank page and raises a ticket as a browser fault. An agent who doesn't know about the XSLT change can lose hours clearing caches. Browser updates on machines that run your ERP deserve the same treatment as any other change to the ERP: a named owner, a test list and a fallback. If your service desk doesn't yet link browser releases to ERP risk, our IT service management work covers that change process, and our ERP team can help scope a Modern UI migration.

Next steps

  • Confirm your Acumatica version, build number and deployment type. If you're on PCS, check whether the October patches for your release are installed.
  • Ask your MYOB Acumatica partner in writing which build includes Acumatica's October XSLT patches, and when they'll apply it.
  • List every screen your staff still open in Classic UI, including customised and partner-built screens. Test each one in Chrome 158 before the update reaches the whole business.
  • If a critical screen fails before the patch is in, set XSLTEnabled to Enabled for the affected users through Group Policy or Intune, in Chrome now and in Edge before Edge 159 arrives. Record an end date well before August 2027.
  • Run the Chrome Legacy Technology Report or a Lighthouse audit across your other internal web apps to find any XSLT you don't know about.
  • If you're on 2024 R2 or earlier, start planning the upgrade now. Budget the Modern UI rework as part of any move to 2026 R2.

Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.

Get my free assessment How we help
Get new articles by RSS