Sergey Vinogradov

Related https://github.com/vaadin/web-components/issues/4184

> could this be prevented without doing https://github.com/vaadin/web-components/issues/4184? Yes, seems to be doable by moving the type conversion logic from the value observer to the value setter: ```diff _valueChanged(newVal, oldVal)...

Though, there is still a question of whether we should show a warning when there is an attempt to set an unparsable value. Right now, it's inconsistent: `integer-field` shows a...

Hey! We are considering introducing a new data provider that will make it possible to support `scrollToItem` for TreeGrid. You can find more details in [vaadin/flow-components#7269](https://github.com/vaadin/flow-components/issues/7269). Feedback is very welcome!

Hey! We are considering introducing a new data provider that is intended to solve this problem. You can find more details in [vaadin/flow-components#7269](https://github.com/vaadin/flow-components/issues/7269). Feedback is very welcome!

Resolved by https://github.com/vaadin/platform/issues/7843 in Vaadin 25. You can now use the new `HierarchyFormat.FLATTENED` feature to prevent scroll position from being affected on `refreshAll`. For more details and to share feedback,...

Depends on - https://github.com/vaadin/flow-components/pull/7668

The workaround is to make your data provider asynchronous, for example by wrapping `callback(items, size)` in a `setTimeout`. This will prevent the recursion that occurs because the grid requests children...

Depends on - https://github.com/vaadin/flow-components/pull/7668

Seems to be the same issue as https://github.com/vaadin/flow-components/issues/7250