Sergey Vinogradov
Sergey Vinogradov
It seems we are already equipped with everything necessary to refactor LitRenderer. We can replace the current `UI.getCurrent()` calls with something like `UI ui = ((StateTree) container.getNode().getOwner()).getUI()`. As for LitRenderer,...
> Vaadin 23 LitRenderer don't use UI.getCurrent() but it has UI instance which it gets in other way. I can confirm that the issue with specifically ComponentRenderer is a regression...
> This is probably obvious already, but while you guys are looking at this it's probably worth reviewing the other examples And I've also opened a [separate ticket](https://github.com/vaadin/flow-components/issues/6757) about refactoring...
Resolved by https://github.com/vaadin/platform/issues/7843 in Vaadin 25.
Reopening, as this issue has been requested to be fixed in Vaadin 24 specifically.
I checked and that PR prevented focus from being reused only when the focus was directly on a cell or row element, which is only one case of the issue....
The root issue is that the virtualizer rounds up `translateY` values. When the row height is fractional, this rounding produces the observed result. The issue is even more noticeable if...
> Without further testting I'd still se the default to 1 thought, Consider a scenario where the user uploads one large file (1 GB) and several smaller ones (1 MB...
I couldn't reproduce the issue in Desktop Safari 14.1. Probably, the issue has been fixed there. https://user-images.githubusercontent.com/5039436/121657979-93a0ba00-caa9-11eb-95d7-0539211b601b.mov
Closing as not planned.