3808623 - SAPUI5 applications fail to load after upgrading to Chromium 153 (Chrome / Microsoft Edge) when XML views or fragments were saved as "UTF-8 with BOM"

After the browser is updated to a Chromium 153-based version (Google Chrome or Microsoft Edge), a SAPUI5 application that loaded correctly on earlier browser versions no longer works. The application typically ran from an optimized build (a Component-preload.js bundle), for example in a productive deployment.

Depending on whether the affected file is a view or a fragment, one of the following is observed.

• When an XML view was saved as "UTF-8 with BOM", the browser replaces the application area with its own XML parse-error page, for example:

  This page contains the following errors:
  error on line 1 at column 1: Unexpected characters outside the root element: 

• When an XML fragment was saved as "UTF-8 with BOM", the application area stays blank and the browser developer console shows an error such as one of the following:

  "openStart" is not valid for aggregation "..." of Element ...
  "close" is not valid for aggregation "..." of Element ...
  

  The exact aggregation name and element in the message vary by application.

• SAPUI5 or OpenUI5 (any maintained version; the blank-page fragment variant is observed with SAPUI5 1.x).
• Google Chrome or Microsoft Edge based on Chromium 153 or higher.
• The application is served from an optimized build that bundles XML views and fragments into a preload file (for example Component-preload.js). This is the default for productive deployments.
• At least one XML view or fragment source file was saved with the encoding "UTF-8 with BOM".

bom unicode encoding xslp parsing xml utf8-BOM 153 , KBA , CA-UI5-COR , Core and Runtime , Problem