If the user has browser extensions installed that send a Message then this message is intercepted by js/elFinder.js:4827, and since the message is not a string of type JSON an exception is returned and the self.sync() method is called.
Using the example of the wappalyzer add-on - a dozen notifications are sent at once by which elFinder sends multiple requests at once to the application backend.
Here is an example for 32 queries through the wappalyzer add-on:
@magik092 Thank you for your suggestion. It seems better to deal with this problem in elFinder.sync(). I opened a related #3572, so I'm going to close this one.
If the user has browser extensions installed that send a Message then this message is intercepted by js/elFinder.js:4827, and since the message is not a string of type JSON an exception is returned and the self.sync() method is called. Using the example of the wappalyzer add-on - a dozen notifications are sent at once by which elFinder sends multiple requests at once to the application backend.
Here is an example for 32 queries through the wappalyzer add-on:![image](https://github.com/Studio-42/elFinder/assets/7090340/c385a794-1902-482d-ac04-df735724db51)