Advanced Minify Script problem R358

Hi all! Since updating to R358, when I export Html5 Web and choose "Minify Mode Advanced", my games no longer run on Itch. The window with the Itch play button will load, but starting the game it only brings up a black screen. If I instead export using the "Simple" minify mode, the game runs as normal (in my case, going to the loader bar and my logo after clicking the Itch play button)

I dropped back to 350 and exported with "Advanced" and it still works fine. I tried another project and had the same results, works in 350, but just a black window in 358.

Has anyone else run into this or a similar issue? It definitely exports much faster in 358, which will be a nice improvement if this problem can be ironed out!

It might be because the version of Closure Compiler used for minifying has been updated. It's difficult to help any more without seeing the project. It's probably best to file an issue about it.

Thanks for the reply! I'll look into filing an issue at the link you provided.

I will note that I did a little more investigation this evening, and based on what files I have on hand, it seems like games worked on before the 4/4/23 Stable r336 release export fine with Advanced Minify from the newest release. Anything I worked on after 4/4/23 now has this export issue in r358.

Of possible help, I do have one project that has saved versions on both sides of that date, with the older copy working fine, and the later copies all experiencing this bug. I'll try to include all this when I file.

Ashley Hello again! I spend several hours cutting down one of my projects and experimenting, and have narrowed it down to 4 sub-event groups that cause the problem. (Works if they are disabled, black screen if they are not.) And as noted earlier, reverting to "simple minify" solves the problem and the game runs as normal.

However, before posting an issue... I have also stumbled upon another large and important fact. This issue seems to be Firefox specific. At the very least, this issue doesn't happen on Edge or Chrome.

I guess my question is, should I still file this as a Comstruct bug? Or is this ultimately on the browser?

Thanks!

File an issue anyway - it's the best way for me to review the situation. If it comes down to a browser issue usually I end up filing an issue with the browser maker.

Will do, thanks!