I’m working on a client app and I don’t have admin rights, so I can’t see if the client has subscribed to this as a feature to test, or if this feature has been rolled out.
Either way, what I am seeing is that when an element has a search in it, saw to show a list of things, and that search is the datasource of the RG, which is hidden and made visible via conditionals. There is a lag time between when the RG is made visible and when the data is displayed. Likely this is intended behavior as a way to speed up page load and help with performance, not needing to load data on hidden elements until they are visible.
One request is to add into this new feature a way for Bubble to automatically after the page has been loaded entirely to fetch the data for the elements that are hidden. I would assume that once the page has been loaded entirely and the page performance has benefited from this new feature, to have an automatic fetch of data would not drag on page load speed performance, but would significantly improve the user experience as the data would be readily available the moment the hidden RG is made visible.
Currently I am having to work around this as I do not want to see the lag time from the moment the hidden RG is made visible and the data is then loaded.
I posted a tip on how to work around it, which ultimately is still loading the data on page load, so the work around doesn’t provide the benefit of the new feature, but does get rid of the lag time.