Description
When the ESF filtering dialog is opened by selecting a custom filtering operands of any type (customer reported for number, also reproduced for string), it is not selected in the operand dropdown, as the built-in operands are.
This seems to occur only the first time when opened, when a filter value has not been set yet.
Framework
Angular
Angular Version
22.0.x
Ignite UI for Angular Version
22.1.x, probably the earlier as well
Component / Area
Grid
Browser
Chrome
Operating System
No response
Command Not Working
Steps to Reproduce
- Open this Stackblitz sample
- Open the ESF on the "Order Product" column
- Choose Text filter -> "Contains (Case-sensitive)" - this is a custom filter
- Observe how the select that should have the filter operand pre-selected when the dialog is opened, appears not to have it selected
To compare, you could choose Text filter -> Not Empty on step 3. The select has the built-in filter operand pre-selected in that case.
Actual Result
When selecting any type of custom filtering operand:
When opening the dialog if the filter was already set, then the dropdown has the correct selection:
Expected Result
When selecting "Not empty" - the select to be correctly pre-populated.
Reproduction URL
https://stackblitz.com/edit/grid-custom-filter-issue?file=src%2Fapp%2Ftree-grid-filtering-custom-sample%2Ftree-grid-filtering-custom-sample.component.ts
Attachments
Description
When the ESF filtering dialog is opened by selecting a custom filtering operands of any type (customer reported for number, also reproduced for string), it is not selected in the operand dropdown, as the built-in operands are.
This seems to occur only the first time when opened, when a filter value has not been set yet.
Framework
Angular
Angular Version
22.0.x
Ignite UI for Angular Version
22.1.x, probably the earlier as well
Component / Area
Grid
Browser
Chrome
Operating System
No response
Command Not Working
Steps to Reproduce
To compare, you could choose Text filter -> Not Empty on step 3. The select has the built-in filter operand pre-selected in that case.
Actual Result
When selecting any type of custom filtering operand:
When opening the dialog if the filter was already set, then the dropdown has the correct selection:
Expected Result
When selecting "Not empty" - the select to be correctly pre-populated.
Reproduction URL
https://stackblitz.com/edit/grid-custom-filter-issue?file=src%2Fapp%2Ftree-grid-filtering-custom-sample%2Ftree-grid-filtering-custom-sample.component.ts
Attachments