Serhii Kulykov

This should no longer be an issue in Vaadin 25 where overlays are not teleported to the document body.

Thanks, I think your approach makes sense so I'll give it a try. We also were not sure about whether to pass `superClass` as a first parameter, IIRC it was...

My original idea from https://github.com/vaadin/web-components/pull/10097 was to use `IntersectionObserver` and only close once target is fully hidden.

This could be probably fixed by changing `focus()` for the submit button to use `focus({ preventScroll: true })`.

Confirmed, here's a reproduction using the web component: ```html Tab 1 Tab 2 Content 1 Content 2 Remove import '@vaadin/tabsheet'; document.querySelector('button').addEventListener('click', () => { const tab = document.querySelector('vaadin-tabsheet vaadin-tab'); const...

Sounds like a grid mode for virtual list to me. The original `iron-list` component supported it but we didn't include it to our fork. Also the Lit Labs virtualizer has...

As we already have `theme` presets for badge-like elements in Lumo, what would be our plan regarding those? Do we keep existing styles and reuse in `vaadin-badge` while also keeping...

We also need to figure out a Flow API and we could discuss it in the same issue (could be also GitHub discussion). Existing API for badges is a bit...

Some more considerations for `vaadin-badge` component to discuss and agree upon, before implementing it: 1. Do we also use the new "badge" a base for `vaadin-multi-select-combo-box-chip` as they seem quite...

Fair enough. We would need to have `BadgeVariant` enum on the Flow side and implement `HasThemeVariant` as well. In case of the `vaadin-badge` component, we probably don't need `badge` theme,...