There seems to be a bug when we have a list in a sidebar.The scroll of list doesn't seem to work when using a real mobile device running as an android app.To replicate the problem, you need a list inserted in a sidebar with more items than the screen can show, so that you would force the scroll.I shared the oml. as an example of the problem.I also added a normal list in the page,that one works correctly, it is only the list in the sidebar that has problems scrolling.
Running the app as an web version can't replicate the issue. For the Preview in Devices seems to let the list scroll, albeit with much difficulty, the scroll moves extremely slow.Comparing the newest version, 2.12.0 with an older one, like 2.8.3.0, there is a change in the OnReady of the Sidebar, where the touchEvents seem to be missing the the newer version, might be the cause of this issue.
Hello @Ionut Vrinceanu
Happy New Year first of all. Just to close this thread, I would like to inform you that this was released in version 2.13.0. If you could take a look and provide some feedback and/or mark this as done it would be great.
Cheers,GM
Hi!
I also have this same issue. I had to get the old version of side bar to have it work again (copy old OutsystemsUI.js, and private functions from side bar). It is working now with the old version.
Apps running on PWA mode and browser work fine, but not on native mode.
If we place a list on a sidebar, it won't scroll on an Android device.
As Ionut said, i also believe that it is related to the missing gestures functions.
This is a major feature on our application (to be able to list pending itens from a sidebar), so please haave a fix for this problem.
The new version of the Sidebar doesn't need to use TouchEvents since it is already part of the new framework that deals with that. The behaviour you're mentioning is an issue that we're trying to fix in time for the next release 2.13.0, under the code ROU-3999 (for reference on the release notes) but we can't guarantee (if we find a possible workaround I'll get back to you in this post - the ETA for the release is December 19).
Just a small remark on the code you shared (nothing to do with this issue) is the fact that you shouldn't be using the OnReady event to create the list that you'll bind to the UI elements and should do that on an Aggregate/Get From Other Sources to make it more performant and more according to best practices that will help to handle the screen lifecycle.
Best Regards,GM
As a workaround, you can use the client action SidebarToggleSwipe and it will make it work. You'll lose the swipe to open and close (toggle) the sidebar but by using the actions to open/close or having the overlay where the Sidebar will be closed you'll be able to have a good experience until we have a fix directly in the product.I'll attach the oml you shared with a new screen both with the usage of SidebarToggleSwipe but also with the logic modified to be more according to best practices, in case you have any doubts. Hope it helps!
Hello @Gonçalo MartinsThanks for the quick response and the workaround.I'll await for the fix, for now I'm using the older version of the sidebar, which has both the fixed scroll and the swipe to open/close the sidebar.
Still, my solution is temporary, since now I'm having a local version of the sidebar, which might get broken but each consequent update to this component might break it. I hopefully expect the fix in the next version. Keep on working.Thanks for the support,Ionut Vrinceanu
Happy to inform you that we were able to fix this on time for the next release 2.13.0, under the code ROU-3999 (for reference on the release notes - the ETA for the release is December 19).
Great news @Gonçalo Martins,
I'll await for the release to test it too. Then I'll close the thread as a solution.
Good work,Ionut Vrinceanu