Sometimes we get an error in the console of the browser. Has this something to do with it?

> We have two ADMs on a page both loading in the same div and replacing the previous. Could it be a conflict somehow? I assigned different ID's.

Yes, this could be problem. How are you replacing them? Call this method in JS before you are deleting the previous one:

fileManager.destroy();

This will clear the JS component's both from page DOM and memory.

When inspecting the page when it loads white, it looks like this:

This is how the code looks after adding the destroy.

Thanks for the quick response :)

So did it work? I see that you put destroy call in window beforeunload event, this should not be necessary. If you are already unloading window/page, then it will already be destoyed. What I meant was, if you are manually removing the component's DIV element when you are switching tabs, you should not do that and call destroy instead.

>  We have two ADMs on a page both loading in the same div and replacing the previous.

$('fileManager').destroy();

fileManager.destroy();

It looks like it has something to do with the width of the component.

This is when I hover over the Gleamtech div.

We are switching to the other tab with javascript. So no access to the fileManager object to destroy.

Are these errors relevant information for you?

I removed one menu-item to see what happens next. But with one menu-item I still get a white page.

Yes, the problem is that you are manully deleting component's html element. Can you disable that code? I replicated the problem. I deleted the element and called destroy and the same error occured even with a single FileManager on the page..

When you are loading a new FileManager instance, destroy is called automaticallty on older instances. But it failes as the previous element no longer exists as you manually deleted it?

We will still fix the behaviour by swallowing exception thrown by destroy method but as the old instance in Javascript is not destroyed completely, it can cause memory issues on your page. So let me know if you are  manually deleting component's html element in your Javascript.

Ok this is fixed now, I will let you know shortly. Even if you remove the DOM element, the error should not throw, as it prevents the loading of the new instance. It was a subtle bug which occured intermittently (due to a buffered function which was called in 200 milliseconds)

Thanks Cem! It works :)

That's good, though I wouldn't expect you to still get that warning for unselectable. Yes we added that warning about error being swallowed but unselectable error originates from breadcrumb navigation component, which I thought was fixed. Maybe this one is from another sub-component. I will check that again.

We have another fix with Version 9.5.6 - April 14, 2025, please check if you still get warning for unselectable. It's not important as it's handled as a warning only but just in case.