
The problem is fixed if I replace the following code: if (!) return t(n.createSwiperInstance(e, n.config)) In August of 2020, we announced the upcoming end of support for the legacy version of the Microsoft Edge desktop app on March 9, 2021. The problem is in in the function SwiperBC.
#MICROSOFT EDGE LEGACY WINDOWS 10#
As part of this transition, the new Microsoft Edge will be available as part of the Windows 10 cumulative monthly security update, which will be released on April 13, 2021. Microsoft strongly recommends that customers build a transition plan to the new Microsoft Edge to ensure an up-to-date browser.
#MICROSOFT EDGE LEGACY CODE#
It looks like the problem is related to the JavaScript code added for the “Improved Asset Loading” experiment and this breakage occurs even if I make the “Improved Asset Loading” experiment Inactive. Its easiest to keep legacy Edge available before the new Edge gets automatically installed, by running the Chromium Edge Blocker Toolkit (at an admin command prompt). This topic describes known issues when using UFT One to test web applications running in the Microsoft Edge Legacy browser. In August of 2020, we announced the upcoming end of support for the legacy version of the Microsoft Edge desktop app on March 9, 2021.
