Serhii Kulykov
Serhii Kulykov
Related issue in the web components repo: https://github.com/vaadin/web-components/issues/4414
There is an existing issue for Tree component: https://github.com/vaadin/flow-components/issues/1547. Since that issue has 12 👍 reactions and we use these as a way of feedback regarding highly requested features, let's...
The main reason for this is that we store references to DOM elements in reactive properties to use them in observers. Example: the `_overlayElement` defined in the `OverlayClassMixin` and set...
Warnings about updates are disabled with https://github.com/vaadin/web-components/pull/9097. I also created https://github.com/vaadin/web-components/pull/9102 to suppress `ReactiveElement` warnings.
Related to #7466
If you want to apply significant changes like moving the overlay to shadow DOM, I'd suggest to do this instead: ```js class CustomPopover extends Popover { static get is() {...
I believe this should be fixed by switching to the native `popover` API in Vaadin 25 instead of teleportation. Until then, I don't think we should change anything in the...
Depends on https://github.com/vaadin/vaadin-combo-box/issues/443
Please note that `DatePicker` has an option to [disable auto-open](https://vaadin.com/docs/latest/components/date-picker#auto-open) which prevents the popup from opening on click and allows user to type a date.
@HerbertsVaadin Thanks for sharing. In your example, `focus()` is called **after** changing the input type. Looks like this fixes the issue for Chrome. In our current implementation, `mousedown` event prevents...