Text_input behavior for updating a session state value is not intuitive for my use-case

[mathcatsand]

Re: Issue 1
When you update some widget parameter with its output, that can lead to those “double submit” scenarios. Here’s one such case I explained in another post:

Mini-tutorial: Initializing widget values and getting them to stick without double presses

I would expect a double click needed in case 2. Say the widget is in sync: it has it’s initial value and is outputting its initial value. st.session_state.A2 = st.number_input( label="What is A2?", min_value=0, max_value=100, value=st.session_state.A2, key='num_A2' ) You click on the widget, so st.session_state.num_A2 is updated instantly and page reloads. After reloading, st.session_state.A2 is updated, as an output from the widget (namely after the widget is mounted). On t…

I believe @Wally’s answer above covers your use case, so I’ll stop there.