App crashes on systems where the `htmlfile` module is corrupted.

[gnh1201]

Summary

Some third-party security software intentionally corrupts the htmlfile module.

As of now, it is estimated that quite a number of security products deliberately break the htmlfile module, likely because it is considered part of legacy Internet Explorer. Of course, that perspective is not entirely incorrect.

As an alternative, the ScriptControl module can be used. Depending on whether the environment is 32-bit or 64-bit, the provider of this module may differ.

Reference: zloirock/core-js#1536

To address this issue, I placed the app/assets/js/core-js-3.49.0.wsh.js file in the dev branch and modified the bootstrap.bat file to prioritize execution in a 32-bit runtime.

Reference: c7f1d66#diff-9f57a0ddd5f7432cbcbf6ab392a8ba9dcd6b71d95be6685e9ef2566a5c6bfc82R50

The 32-bit version of ScriptControl is typically provided by Microsoft (Windows built-in modules), whereas the 64-bit version is usually provided by third parties. Therefore, the following component must be installed:

Reference: https://tablacus.github.io/scriptcontrol_en.html

I apologize for the time it took to prepare this patch. Thank you.

Related articles (issues, PRs, links, etc.):

• CScript is Windows and not welsonjs example seems miss leading #308
• c7f1d66#diff-9f57a0ddd5f7432cbcbf6ab392a8ba9dcd6b71d95be6685e9ef2566a5c6bfc82R50
• Crash fix in WSH runtime zloirock/core-js#1536
• object-create在非浏览器环境下会报错 zloirock/core-js#1395
• ActiveXObject fallback in core-js zloirock/core-js#1534
• https://tablacus.github.io/scriptcontrol_en.html

[linear]

CAT-104

[gnh1201]

Fixed.