You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you click on a tree node and it loads some content via xhr and then click on another node loading content via xhr and then go back to the first item you clicked on no content will be loaded on the second click. The element to recive the content will update its title and the content will be cleared out but no new content gets loaded and therefore none gets set.
To duplicate this issue simply
download the latest copy of the code from the repository
open the Demos/index.html file
click on the "Development Notes" item in the tree menu - you should see the development notes
click on the "XHR: Lorem Ipsum" item - you should see the basic lorem ipsum page
now click back on the "Development Notes" item and now although the panels label changes the content area of the panel will be left empty. Also if you click back on the Lorem Ipsum item it will also change the panel title and content remains empty
I have tried looking through the code and can't work out quite what its doing in order to locate the bug. Hoping you might have some ideas and/or a fix?
The text was updated successfully, but these errors were encountered:
Just comment this code
if (content.content){
content.content = MUI.Content.processFilters(content);
Browser.ie6 ? content.fireLoaded.delay(50, content) : content.fireLoaded();
return;
in content.js :)
If you click on a tree node and it loads some content via xhr and then click on another node loading content via xhr and then go back to the first item you clicked on no content will be loaded on the second click. The element to recive the content will update its title and the content will be cleared out but no new content gets loaded and therefore none gets set.
To duplicate this issue simply
I have tried looking through the code and can't work out quite what its doing in order to locate the bug. Hoping you might have some ideas and/or a fix?
The text was updated successfully, but these errors were encountered: