You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Manfred Bergmann <mb...@software-by-mabe.com> on 2016/11/22 17:13:26 UTC
Kendo UI AjaxtreeView testing for rendered nodes
Hi.
I'd like to unit-test if and which tree elements have rendered.
How could I do that? It seems the rendered HTML only has the <div/> element
of the tree view.
Manfred
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Kendo-UI-AjaxtreeView-testing-for-rendered-nodes-tp4676242.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Kendo UI AjaxtreeView testing for rendered nodes
Posted by Sebastien <se...@gmail.com>.
IIRC, the static TreeView is based on the underlying HTML, therefore no
call is made to [lazy]load the content.
About the generated content tree (lazy mode), I guess it can be retrieve by
an HTML id.
This page will be interesting for you:
http://docs.telerik.com/kendo-ui/intro/widget-basics/wrapper-element
Hope this help,
Sebastien
On Wed, Nov 23, 2016 at 11:09 AM, Manfred Bergmann <mb...@software-by-mabe.com>
wrote:
> Martin Grigorov-4 wrote
> > On Wed, Nov 23, 2016 at 10:49 AM, Manfred Bergmann <
>
> > mb@
>
> > >
> > 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.
>
> OK, yeah.
> That means it's practically not possible to unit-test the correct
> rendering?
> I could the use the static TreeView approach.
> But does it support lazy loading of tree node?
>
>
>
> Manfred
>
Re: Kendo UI AjaxtreeView testing for rendered nodes
Posted by Manfred Bergmann <mb...@software-by-mabe.com>.
Martin Grigorov-4 wrote
> On Wed, Nov 23, 2016 at 10:49 AM, Manfred Bergmann <
> mb@
> >
> 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.
OK, yeah.
That means it's practically not possible to unit-test the correct rendering?
I could the use the static TreeView approach.
But does it support lazy loading of tree node?
Manfred
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Kendo-UI-AjaxtreeView-testing-for-rendered-nodes-tp4676242p4676256.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Kendo UI AjaxtreeView testing for rendered nodes
Posted by Martin Grigorov <mg...@apache.org>.
On Wed, Nov 23, 2016 at 10:49 AM, Manfred Bergmann <mb...@software-by-mabe.com>
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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Kendo UI AjaxtreeView testing for rendered nodes
Posted by Manfred Bergmann <mb...@software-by-mabe.com>.
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?
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.n4.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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org