Elementor 3.1 doesn’t display properly in Microsoft Edge Legacy

  • Resolved joneiseman

    (@joneiseman)


    4 years, 1 month ago

    After updating to version 3.1, the Elementor designed pages no longer display properly in Microsoft Edge Legacy. When I revert to version 3.0.16 the page displays fine in Microsoft Edge Legacy (see this in https://staging2.mafw.org). If you are dropping support for Microsoft Edge Legacy (for displaying the web page), you should update this page: https://elementor.com/help/requirements/
    Here’s the Microsoft Edge version I see the problem in: Microsoft Edge 44.18362.449.0
    Turning off Experiments does not fix the problem. When I look in the Developer’s console I see the following JavaScript error: ‘wp’ is not defined
    This error shows up in 3.1 but not in 3.0.16.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter joneiseman

    (@joneiseman)

    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. The problem is in frontend.min.js in the function SwiperBC. The problem is fixed if I replace the following code:

    if (!elementorFrontendConfig.environmentMode.isImprovedAssetsLoading) return t(n.createSwiperInstance(e, n.config));
var i = elementorFrontendConfig.environmentMode.isScriptDebug ? "" : ".min";
import("".concat(elementorFrontendConfig.urls.assets, "lib/swiper/swiper").concat(i, ".js?ver=5.3.6")).then(function () {
    return t(n.createSwiperInstance(e, n.config));
});

    With this line:

    return t(n.createSwiperInstance(e, n.config));

    I think the Microsoft Edge Legacy browser doesn’t like the import statement inside a function definition (it expects it to be at the top level).

    Another thing I noticed is that frontend.min.js is different than frontend.js (it isn’t just a minified version of frontend.js). For example, I see frontend.min.js has the import within a function but frontend.js does not.

    • This reply was modified 4 years, 1 month ago by joneiseman.
    • This reply was modified 4 years, 1 month ago by joneiseman.
    • This reply was modified 4 years, 1 month ago by joneiseman.
    Thread Starter joneiseman

    (@joneiseman)

    Now I put version 3.1.1 on both staging2.mafw.org and on mafw.org. On mafw.org I fixed frontend.min.js (as shown in my previous post). You will see the pulldown “Rides” navigation menu is not working in staging2.mafw.org (when viewed in the Microsoft Edge Legacy browser).

    Hi,Since you are using our Pro features on your website, you’ll need to open a support ticket at my.elementor.com.

    www.remarpro.com rules state that commercial products are not supported here.

    I ran into an issue similar to that reported by joneiseman, in that certain elements were no longer visible when viewed on MS Edge (virtual OS install using a trial Windows 10 via VirtualBox on macOS).

    MS Edge identified a script error in frontend.min.js:
    /wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.1.4

    I’m using the current version of Elementor (3.1.4), and fwiw also using Elementor Pro (3.1.1). That said, the error persisted after deactivating all other plugins (including Pro) and setting the theme to TwentyTwenty. So it seems this issue may not be related to Elementor Pro.

    I replaced the code (as per joneiseman) in frontend.min.js (regular Elementor, not Pro). The script error went away and the affected elements appeared properly.

    Thank you @joneiseman!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Elementor 3.1 doesn’t display properly in Microsoft Edge Legacy’ is closed to new replies.