Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug with Tree Plugin #99

Open
richard-myers opened this issue Apr 3, 2011 · 5 comments
Open

Bug with Tree Plugin #99

richard-myers opened this issue Apr 3, 2011 · 5 comments
Milestone

Comments

@richard-myers
Copy link

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

  1. download the latest copy of the code from the repository
  2. open the Demos/index.html file
  3. click on the "Development Notes" item in the tree menu - you should see the development notes
  4. click on the "XHR: Lorem Ipsum" item - you should see the basic lorem ipsum page
  5. 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?

@richard-myers
Copy link
Author

Forgot to mention that I've tried this in both Safari 5 and Firefox 4 on a Mac and both are showing the same problem.

@richard-myers
Copy link
Author

Why has this been closed? It still seems to be happening on latest copy of the code?

@eerne
Copy link
Contributor

eerne commented Apr 3, 2011

github says you closed it

RichardM87 closed issue 99 on mui/mochaui about 10 hours ago

@richard-myers
Copy link
Author

@eerne - any chance you know how to unclose an issue? I never realised I'd closed it :-s

@cdotyone cdotyone reopened this Apr 5, 2011
@Ango
Copy link
Contributor

Ango commented Aug 12, 2011

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants