@christophemarois Thanks for the code. I think that’s not using Onsen UI page animations at all, only custom Vue transitions. Even the ons-navigator included there is not doing anything, you can just replace it with a simple div.
I’ll try to fix the mentioned GitHub issue when I have some time, hopefully in a few weeks.
@Fran-Diox I did went with onInfiniteScroll option but because I had to sort my table after based on distance, gradual loading just wouldn’t get an accurate sort when the data isn’t all loaded.
@munsterlander Just what I had in mind, I had first time users preload the data during app startup and saved them into web storage, then appended them into the page with jQuery .html(). No more load time!
Hey Fran. The behavior seems worse with the new release of Onsen (2.7). It was so bad, I replaced my use of the Onsen TabBar component with a really simple one I wrote myself and everything is working now.
If I have an extra bit of time I’ll try to make a reproducible case for you so you can fix it in Onsen.
The one mentioned in the guide link I posted. You can use Crosswalk plugin if you want to support older versions of Android. The reason is that the old Android web view does not implement many features that Onsen UI relies on. From simple Promise to Set/Map, for example.
@mmike Well, the only possible issue I can think about is timing. Make sure that when you populate the inputs, the elements are already attached to the DOM. The best moment to do this is during page’s init event.
@Gilad-Tiram Hmm, I’ve never tried to do something like that so I’m not sure what kind of problems might appear, but perhaps you can just put the “content elements” in Shadow DOM and let the pages run normally: