I noticed during development that when using st.tabs with either st.Dataframe or AgGrid in its containers, the first selection operation always triggers a table refresh. The difference is that st.Dataframe doesn’t lose its selection, while AgGrid clears it. Of course, the selection results are recorded in st.session. When using two st.number_input widgets within a st.tabs container, no matter which st.number_input is interacted with first, moving the focus to the second one will inevitably cause a page refresh, leading to a reset of all interactions. When I move either st.Dataframe or AgGrid outside of st.tabs, the refresh and reset phenomenon during interaction disappears. This is what I observed, but I don’t understand why it happens. I would appreciate any guidance. Thanks!
It look like the data doesn’t have the “new” update session_state. I think the easy fix, i would try will be a st.rerun after the st.session.product is loading.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.