Community
Participate
Working Groups
When scrolling down to the last item on the first level of a tree and expanding the last item we send a request that has both the expansion as well as the topItemIndex property: {"head":{"requestCounter":37},"operations":[["set","w1",{"focusControl":"w6"}],["set","w120",{"expanded":true}],["notify","w6","Expand",{"item":"w120"}],["set","w6",{"topItemIndex":97}]]} The server does not honor the topItemIndex so it only sends one or two items that would fit into the viewport as if the tree is still srolled to the bottom. Sending the expand and topItemIndex in two requests works as expected.
(In reply to comment #0) > When scrolling down to the last item on the first level of a tree and > expanding the last item we send a request that has both the expansion as > well as the topItemIndex property: > > {"head":{"requestCounter":37},"operations":[["set","w1",{"focusControl": > "w6"}],["set","w120",{"expanded":true}],["notify","w6","Expand",{"item": > "w120"}],["set","w6",{"topItemIndex":97}]]} > > The server does not honor the topItemIndex so it only sends one or two items > that would fit into the viewport as if the tree is still srolled to the > bottom. > > Sending the expand and topItemIndex in two requests works as expected. Currently, topItemIndex property is handled by TreeLCA and expanded property by TreeItemLCA. As TreeLCA is visited first, topItemIndex is set before the item is been expanded. I think that it's not possible (or too hard) for the web client to set these two properties in a same request (click on the expand sign and scroll with mouse wheel before the request is sent). Anyway... we have plans to process the message sent by the client directly (respecting the order) and not using LCAs in the future. But probably this will happen in RAP 2.2.
