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

CellEditExit is calling twice when I change to another Cell in different Row #11154

Closed
Andresrf13 opened this issue Mar 2, 2022 · 0 comments · Fixed by #11193
Closed

CellEditExit is calling twice when I change to another Cell in different Row #11154

Andresrf13 opened this issue Mar 2, 2022 · 0 comments · Fixed by #11193
Assignees
Labels
🐛 bug Any issue that describes a bug ❌ status: awaiting-test PRs awaiting manual verification

Comments

@Andresrf13
Copy link

Description

The CellEditExit is triggered twice when I change to another Cell in a different row without closing the editing popup. The first event is for the current cell and the second time is for the new cell clicked.

  • igniteui-angular version: 12.3.8 & 13.0.0
  • browser: tested in Chrome

Steps to reproduce

  1. Create an igx-grid with some data (at least two rows).
  2. Add the CellEditExit event with a handler to inspect (use a console.log or debugger)
  3. Add the rowEditable input to the igx-grid equals true.
  4. Enter in the edit mode of any cell of the first row.
  5. Without closing the popup (cancel, done) click on another cell in a different row.
  6. Inspect the call in the CellEditExit handler, you will get the event trigger twice.

Result

The CellEditExit event is calling twice.

Expected result

The CellEditExit should be called just for the first cell.

Attachments

You can check the behavior in the stackBlitz sample:

https://stackblitz.com/edit/angular-crstev?file=src/app/grid/grid-row-editing-sample/grid-row-editing-sample.component.ts

@Andresrf13 Andresrf13 added the 🐛 bug Any issue that describes a bug label Mar 2, 2022
@Volen99 Volen99 added 🛠️ status: in-development Issues and PRs with active development on them and removed 🆕 status: new labels Mar 7, 2022
@hanastasov hanastasov added ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged. 🛠️ status: in-development Issues and PRs with active development on them and removed 🛠️ status: in-development Issues and PRs with active development on them ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged. labels Mar 9, 2022
@Volen99 Volen99 added ❌ status: awaiting-test PRs awaiting manual verification and removed 🛠️ status: in-development Issues and PRs with active development on them labels Mar 14, 2022
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: awaiting-test PRs awaiting manual verification
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants