Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IgxGrid] "CLEAR FILTER" button behaves itself in a different way depending on whether filtering conditions are already applied to the grid or not. #15193

Open
norikois opened this issue Dec 25, 2024 · 0 comments
Assignees
Labels
🐛 bug Any issue that describes a bug 👀 status: in-review Issue is currently being reviewed 🆕 status: new

Comments

@norikois
Copy link

Description

[IgxGrid] "CLEAR FILTER" button behaves itself in a different way depending on whether filtering conditions are already applied to the grid or not.
(1) If some filtering conditions are applied to the igx-grid, clicking "CLEAR FILTER" clears all the conditions.
(2) If no filtering condition is applied to the igx-grid, clicking "CLEAR FILTER" reverts the filter conditions back to that when the dialog was opened.

  • igniteui-angular version: 18.x
  • browser: Any. No dependency on browser

Steps to reproduce

  1. npm ci and npm start the attached sample.
  2. Apply several filter conditions to one of the columns. For example, to the "Order Date" column, apply two filter conditions, one filter condition is "=Today" and the other is "=Yesterday", combine them with "Or" operator and click the "APPLY" button.
  3. Open the custom filter dialog again at the "Order Date" column and click "CLEAR FILTER" button.
    -> The applied conditions are all cleared. This is the behavior (1).
  4. Click vertically-three-dotted icon at the "Order Date" column, click "=Today", which opens the filter dialog with the "=Today" condition on.
  5. Add a second condition "=Yesterday" on the dialog and then just click the "CLEAR FILTER" button.
    -> It reverts back to single "=Today" condition which was on when the dialog was opened. This is the behavior (2).

Result

The "CLEAR BUTTON" behavior is different.

Expected result

The "CLEAR BUTTON" behavior should be consistent.

Note1

One of our customers is migrating their application from 12.x to 18.x. According to them, as far as they gave it a test, this is one of the behavioral changes they've found and they would like the Clear button to clear all the conditions in the both cases because it was the behavior in v12.x.

Note2

In an internal discussion, UX point of view should be taken into consideration in deciding how this button should behave.

Attachments

c00240466-app3.zip
c00240466-app3-recording-2024-12-25-103636.zip

@norikois norikois added 🐛 bug Any issue that describes a bug 🆕 status: new labels Dec 25, 2024
@ChronosSF ChronosSF assigned ChronosSF and gedinakova and unassigned ChronosSF Jan 2, 2025
@gedinakova gedinakova added the 👀 status: in-review Issue is currently being reviewed label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Any issue that describes a bug 👀 status: in-review Issue is currently being reviewed 🆕 status: new
Projects
None yet
Development

No branches or pull requests

3 participants