Textbox with trigger=true clears itself after submitting value

[lo5]

Q SDK Version, OS
0.6.0

Steps To Reproduce
Run this example: https://github.com/h2oai/qd/blob/master/py/examples/table_filter_backend.py

Actual behavior
Search field is cleared as soon as you type.

Expected behavior
Search field should not be cleared.

[mturoci]

Since trigger submits the value and rerenders the component, there is no way as of now to keep the state on client. I consider clearing the field after submitting a normal UX (visual feedback something happened) - it makes sense in pig latin example. However, if you don't want to clear the field after submit, you can specify the textbox like this:

ui.textbox(name='search', label='Search', placeholder='Enter a keyword...', trigger=True, value=q.args.search)

[mturoci]

The only UX problem with that though is losing focus on search field itself. We can probably add focus prop that would focus the component on render.

cc @lo5

[lo5]

Having to set value=q.args.search is extra work (and ugly) from the app author's perspective.

One way to address this is to make each form component update its value in the local copy of the card.
Today, it only sets the changed value in args and either syncs or gets submitted when some other component invokes a sync.

if, say, the textbox stored its value in the local copy of the card, then the caller doesn't need to explicitly set the value on the roundtrip.

[lo5]

Let's table this for a while. I need some time to mull it over.

[lo5]

We can probably add focus prop that would focus the component on render.

This would be useful. How would you achieve this exactly?

[mturoci]

This would be useful. How would you achieve this exactly?

We can add a ref to the textbox and simply call ref.current.focus() in init function.

[mturoci]

Note that this is far broader problem than just textbox. It clears the value in same manner for every component with trigger=True.