I have worked on this a bit, and I think I know the cause of the problem. Jered is making inserts into the tree. The way this is handled, is that the tree first prepends javascript to create a new placeholder in the tree for the new node, and then it relies on the wicket ajax to replace the node it just created with the new data that it got from XMLHttpRequest.
What's happened, is that the script that creates the new node, Wicket.Tree.createElement(), creates a <script> tag. Then wicket seems to attempt a swap of the outerHTML property. The script tag in IE doesn't seem to properly support outerHTML. When you inspect the code after the swap you get something like <SCRIPT id=tree10_17 outerHtml="<table class="wicket-tree-content" id="tree10_17">[lots of html goes here]</SCRIPT> Because of that, it doesn't show up properly at all. Firefox must either support outerHTML correctly, or maybe it uses a different method of AJAX. I changed the tree.js file so that it created a div tag instead of a script tag and it Works For Me™ For what reason was a script tag created instead of a normal markup container? John McKay Matej Knopp-2 wrote: > > That's really weird. updateTree() should work in all supported browsers. > > -Matej > > On Mon, Mar 17, 2008 at 6:34 PM, jeredm <[EMAIL PROTECTED]> > wrote: >> >> One more note. The updateTree() call did work in Firefox, but not in >> IE6 or >> IE7. >> > -- View this message in context: http://www.nabble.com/LinkTree-Node-Refresh-tp16041813p16572697.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
