On Wed, Nov 23, 2016 at 10:49 AM, Manfred Bergmann <[email protected]> wrote:
> An interesting thing is that when I tell the browser to show me the html > source of the page (a page with only the AjaxTreeView). > Then I just see this in the body: > <body> > <div> > <div id="treeview1"></div> > </div> > </body> > > Even though I can see the tree nodes are displayed. > > When using the examine element function of the browser (Firefox) I suddenly > see the tree nodes as <li> list elements in the inspector. > Can somebody explain what's happening there? > This is how JavaScript applications work. The server (Wicket in current case) generates part of the final HTML. Once loaded in the browser (i.e. on domready) the JS takes over and generates the rest. > > > Another question regarding drag & drop in the treeview. > The Kendo UI page shows it's possible. How would I do that in Wicket? > > > > Manfred > > -- > View this message in context: http://apache-wicket.1842946.n > 4.nabble.com/Kendo-UI-AjaxtreeView-testing-for-rendered- > nodes-tp4676242p4676253.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
