Can you please click F12 in the browser and give us a screenshot of any errors shown in the JavaScript console? Thank you.

(That's a template snippet, but F12 usually gives us some good hint. :) )

I don't see anything in the console or network requests that is failing.

I was able to reproduce it in the following way:
1) Open the email templates screen of a survey with attachments, with or without errors.
2) Click on an attachment to open KCFinder, and close it
3) Press the Back button of the browser

Considering that it only happens after you have opened the KCFinder and apparently it hangs loading a gif, it must be something related to a loader that must be set the first time you open the kcfinder and it must remain set.

@gabrieljenik can you take this and make it a priority? It seems pretty bad to me.

Well, for me, pretty bad would be not allowing people to take surveys :)
This is not good, obviously, but many things are still working even with this bug :)

This is very hard to reproduce.
Couldn't reproduce the ticket problem exactly as described, so we focused a bit on the problem "going back" situation mentioned in the comments.

I could only reproduce the crash itself in Vivaldi (it stays in pending loading the gif and I have to kill the process no matter what). In Chrome it hangs a little but you can close the tab.

The first thing I see, which doesn't seem right to me, is that when you close the modal the history of the browser is modified, so when you press Back it doesn't go to the previous page, but instead tries to load back what was in the iframe. But that's not the problem.

Until the commit prior to 16aa81f2810abbcba24a22ae09b5d85b8b8b44fc it worked that way, but it didn't hang, and when I pressed back again it worked OK. In 16aa81f2810abbcba24a22ae09b5d85b8b8b44fc we updated the KCFinder jquery and from there the problem started.

So @tibor.pacalat, could you please try to reproduce it on this commit 16aa81f2810abbcba24a22ae09b5d85b8b8b44fc?

Thanks

I could not reproduce this on this commit, however this commit is 5.x and I have reported issue on 6.x where I can still consistently reproduce it.

Which browser do you use?

I have all browsers installed, but I tested this on Chrome Version 117.

@tibor.pacalat
Are you sure you don't have any warnings on the console?
Of any kind?

We were not able to reproduce it.

Something that happened in one of our tests was beacuse of a cookie issue that made the JS to fail.
Maybe that could be happening on your end.

Our end is not the same: We are using Linux + Chrome or Windows + Chrome.
I guess the best is to have this doen by someone who has Mac.

I will deassign it.