Avoid serving legacy JavaScript code in modern browsers

We didn’t find any specific issue on our end.

Using legacy code is acceptable, especially when maintaining backward compatibility is necessary. Since not all of our users operate in the same environment. The issue you mentioned appears to be triggered by third-party plugins, even within build assets, which are outside our control.

Addressing compatibility with every possible external asset would lead to over-engineering and isn’t feasible in practice.

We always aim for a balance between stability and flexibility. Please let us know if there’s anything else we can assist you with.