Grid - Filterrow - selecting operator triggers filtering & makes wide tables unusable about kendo-react HOT 3 CLOSED

Changing the operator triggers filter always for some reasons:

• Some operators works without value: isNull, isNotNull, isEmpty etc.
• The programmer could handle the filter event and decide if he wants to process the new filters or not. Modify the value automatically or to ignore them. Thus the coder have full control.
• Empty input is still a value for the string columns.
• You could could always set back the filter prop to the grid, without new data prop.
• If we fire events conditionally

The second one is real issue. We will fix it by adding ensuring the width of the data container is set even if there is no data to match the header.

from kendo-react.

Yeah, you are right its in between. We have full control, so i will add some consistency checks in the callback.

from kendo-react.

We have added empty message, localizated by default, and can be further customized with custom components using the inside the Grid. It is spanned thru the whole body of the grid, so the scroll will not disappear anymore after filtering returns empty data.

Will be available shortly in next uploaded dev version.

from kendo-react.