Serhii Kulykov

There are technical reasons why the items behave like that mentioned at https://github.com/vaadin/vaadin-combo-box/issues/529#issuecomment-330756964 > we are using iron-list, and that positions the items absolutely, so the width of the items...

I need to clarify that this is currently not in our short-term roadmap. We would need to do some prototyping first. Compared to grid, there is an additional challenge related...

Thanks for the issue. We can consider having default styles for slotted links to make them look better.

The problematic code referenced in the original issue can be found here: https://github.com/vaadin/web-components/blob/9ac203399b1cf0b4d52480d3de4fa8e5b36de662/packages/select/src/vaadin-select.js#L386-L393 Possible solution: check for `event.composedPath()[0]` and ignore click events in case it's `` A more clean solution:...

Prototype branch with `validate()` method calls replaced with `_requestValidation()` which checks for `manualValidation` property: https://github.com/vaadin/web-components/compare/proto/manual-validation Note: if we decide to also use this in Flow like suggested above, we might...

Hiding these buttons is already doable with CSS e.g. using `::part()` selectors like this: ```css vaadin-rich-text-editor::part(toolbar-group-block), vaadin-rich-text-editor::part(toolbar-group-rich-text), vaadin-rich-text-editor::part(toolbar-group-glyph-transformation) { display: none; } ```

Closing in favor of #7481.

@dependabot rebase

I think it's related to #1384. As mentioned there, in `vaadin-text-area` we set hover background differently: > The text-field hover and activation effect is done using a pseudo element. That...

Thanks for the issue. We had another problem reported previously at https://github.com/vaadin/web-components/issues/7744 where tooltip wasn't shown correctly with not fully visible cell, so the current behavior is by design: https://github.com/vaadin/web-components/pull/7749