Not really. "prerendered" is a performance optimization, and as such a trade-off. The best solution would be a treeview that is optimized enough itself to not needing the prerendered option. But that isn't a workaround and involves much more work.
Jörn On Tue, Oct 7, 2008 at 9:59 AM, pjdevries <[EMAIL PROTECTED]> wrote: > > Thanks Jörn. > > I was afraid you might say something like that :( Apart from not > knowing how to do that, it will also make my servers side code more > complex. Can you think of any other nifty work around? > > On Oct 6, 7:01 pm, "Jörn Zaefferer" <[EMAIL PROTECTED]> > wrote: >> If you use prerendered, you have to read the cookie on the serverside >> and render the tree accordingly. Otherwise you have to disable >> prerendered to be able to use cookie persistence. >> >> Jörn >> >> On Mon, Oct 6, 2008 at 6:08 PM, pjdevries <[EMAIL PROTECTED]> wrote: >> >> > I'm usingtreeview(version 1.4.1) with the 'prerendered' option in >> > combination with 'cookie' persistence. This seems to work fine until >> > the page with thetreeviewis build from scratch (as opposed to >> > refreshed as a result of pressing the browser back button for >> > instance). Because I build the prerenderedtreeviewwith all nodes >> > collapsed, all list items initially have the 'expandable' class set. >> > After the persistence logic has done it's thing, one would expect the >> > 'expandable' classes of the expanded nodes to have changed to >> > 'collapsable' but unfortunately that is not the case. >> >> > Is there a simple solution or workaround for this problem? >
