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

Change detection runs far to often (dxDataGrid) #702

Closed
MarioGruda opened this issue Mar 4, 2018 · 3 comments · Fixed by #748
Closed

Change detection runs far to often (dxDataGrid) #702

MarioGruda opened this issue Mar 4, 2018 · 3 comments · Fixed by #748
Assignees
Labels

Comments

@MarioGruda
Copy link

devexteme version: 18.1.1 beta
devextreme-angular version: 18.1.1 beta
  • Specify the type of the issue (check one with "x"):
    [x ] bug Report

It looks like the dxDataGrid is subscribing to an onmouseover event (maybe other or further events) within the angular zone. This causes the angular Changedetector to run far too often.

Here is a small example: https://stackblitz.com/edit/angular-o6xaio

best regards

@MarioGruda MarioGruda changed the title Changedetection runs far to often dxDataGrid Changedetection runs far to often (dxDataGrid) Mar 4, 2018
@GoshaFighten GoshaFighten self-assigned this Mar 5, 2018
@GoshaFighten GoshaFighten removed their assignment Mar 5, 2018
@ovchinnikov ovchinnikov self-assigned this Apr 4, 2018
@NickMitrokhin NickMitrokhin changed the title Changedetection runs far to often (dxDataGrid) Change detection runs far to often (dxDataGrid) Apr 18, 2018
@ovchinnikov
Copy link
Contributor

After additional testing, we found regression in the existing code. We reverted these changes and will make an update here once we find a more efficient solution.

@SanderElias
Copy link

I'm seeing the same behaviour, plus an overly eager calling off all helper functions. I opened up #839 for this. The excessive calling off helpers is on top of this.

@LexDX
Copy link

LexDX commented Dec 23, 2019

After thorough research, we came to the conclusion that it is not possible to change the current behavior without rewriting a big part of our DevExtreme package. Such a huge change can affect a lot of our existing customers and break their projects. We are unable to introduce such changes in minor versions without thorough testing. So, we will consider enhancing the current behavior in future versions of our library but I can't provide you with any ETA.

@LexDX LexDX closed this as completed Dec 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants