Tatu Lund

As a workaround it is possible to extend `GeneratedVaadinRadioButton` ``` public class Radio extends GeneratedVaadinRadioButton implements ItemComponent, HasComponents { Radio() { } public void setValue(boolean value) { getElement().setProperty("checked", value); }...

I have seen two cases for this one. 1. Use it in single select Grid in custom selection column similar to checkboxes in multiselect Grid 2. Use it as building...

> Therefore we should provide this feature also for grid rows. The easiest change would be to simply let getRow(int) do the scroll by changing the internal call to getRow(rowIndex,...

Ah, now I get it. I implemented it that way in order to not break things, that is why getRow(int) does not scroll and getRow(int, boolean) does that.

The change seems not to break existing tests: https://github.com/vaadin/flow-components/pull/8205

As a workaround you can hide the spinner with CSS. Add class name "empty" to the TabSheet using `tabSheet.addClassName("empty")` when the last tab is removed. https://vaadin.com/docs/latest/components/tabs/styling ``` vaadin-tabsheet.empty::part(loader) { display:...

A bit evolved workaround is to have clear button only in the date field and clear both fields with single click: ``` dateTimePicker.getElement().executeJs(""" $0.__datePicker.clearButtonVisible=true; $0.__datePicker.$.clearButton.addEventListener('click', (e) => $0.__timePicker.clear()); """, dateTimePicker.getElement());...

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

Fixed in Vaadin 23.3 / 24.0 and newer according to linked PR, why this is not closed?

The workaround is to use count callback ``` private void setDataProvider(Grid grid, List items) { var dataView = grid.setItems(query -> { query.getLimit(); if (items.isEmpty() || query.getOffset() >= items.size()) { return...