Nerijus

Returning to this problem, why we can not simply define forward references with real types and add `from __future__ import annotations`? I looked at bpo-41370 and to get correct types...

Tried 1st solution, the problem still remains.

Actually the problem is with input element updates. I need to update only sibling dropwdown element and keep _input_ the same. But it seems I can't prevent that. If some...

@dddomodossola element properties are not synchronized with attributes, maybe we can handle them differently? In such cases updates will not be triggered. I have seen in snabbdom virtual dom library,...

Solution to my problem is not to store received value to attributes dictionary. But I think that attributes and properties should be updated separately anyway.

> it could be feasible to update only attributes avoiding to replace the widget I mean update properties not attributes. Attributes can be kept the same. In static html, when...

@dddomodossola I will try to implement some prototype with properties in my fork.

My script is not directly related to that problem. You can read more about properties and attributes here: https://stackoverflow.com/a/6004028 and https://blog.fullstacktraining.com/html-attributes-vs-dom-properties/ We don't always need to update attributes and thus...

Remi in all places where I looked is retrieving properties via sendCallbackParam (eg. param['value'] = document.getElementById('123').value

Btw, you can look at https://github.com/snabbdom/snabbdom/blob/master/src/modules/props.ts the code to update properties is quite simple, but Remi must allow (and track?) property updates in addition to attributes. Probably there should be...