Angular detect changes is triggered on every mouse move

Angular detect changes is triggered on every mouse move

Posted by: roman-huerliman on 14 September 2017, 12:11 pm EST

• 

  roman-huerliman

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  Hi
  
  We have the issue, that as soon as we use the wj-list-box and the wj-combo-box, that then the detect changes mechanism of Angular is triggered on every mouse move.
  
  How can we change this behavior?

  In our research we have seen, that the it is presumably the pointerout trigger which causes this behavior. Your mouse move triggers should run outside angular zones.
  
  Please note, I only have tested the two components wj-list-box and the wj-combo-box. It is well possible, that this is behavior emerges with other components too.

  Regards,
  
  Roman

• 

  roman-huerliman

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  You can test this by editing your InputIntro sample:
  
  add this to the app.ts:

   
  public get countryList() {
              console.log('getter called')
              return this.countries;
          }
  
          public set countryList(countries: string[]) {
              this.countries = countries;
          }
  

  and change the itemsSource in the app.html to countryList:

  
   <div class="app-input-group">
                      <label>Non-Editable</label>
                      <wj-combo-box [itemsSource]="countryList"
                                    [isEditable]="false">
                      </wj-combo-box>
                  </div>
  

  You then will see, that the getter to the countryList is called on every mouse move

• 

  skochan

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  Hi,

  We are investigating this issue. We shall update you on this soon.

  Thanks,
  
  Abhishek

• 

  manish-gupta1

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  Hi,
  
  Thank you for reporting the issue and sorry for the late reply.
  
  We are able to replicate the issue and it looks like a bug. Hence, this issue has been escalated to the concerned team for further investigation with tracking id 278258. We will let you know as soon as we get any update on this issue.

  Thanks,
  
  Manish Kumar Gupta

• 

  roman-huerliman

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  Hi,
  
  Any progress on this?

  Regards, Roman

• 

  manish-gupta1

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  Hi,
  
  This issue is still with the development team.

  Thanks,
  
  Manish Kumar Gupta

• 

  roman.huerlimann

  • Post Options:
  • Link
    Copy

  Posted 10 October 2017, 7:02 am EST

  In the new build 5.20172.359 in the release notes (change log) it is mentioned:
  
  [Angular] Wijmo components don’t cause change detection anymore for frequently triggered events like mousemove, to which components are subscribed internally.

  I was hoping, that this change is fixing this issue here, but I just checked and unfortunately this is not the case. The get-methods are still called during the mouse move event with the new version.

  So when is it planned to fix this issue here?

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 11 October 2017, 7:20 am EST

  Hi Roman,
  
  Thanks for reporting this.

  I have informed to the development team for further investigation.

  ~Manish Kr Gupta

• 

  patrick.maurer

  • Post Options:
  • Link
    Copy

  Posted 21 February 2018, 8:48 am EST

  Is there any progress on this issue? We are increasingly suffering from this behavior…

• 

  roman.huerlimann

  • Post Options:
  • Link
    Copy

  Posted 2 March 2018, 6:33 am EST

  We have an absolut blocker with this now, if this can’t be changed within the next two weeks we have to replace Wijmo with another library!

• 

  m.geri

  • Post Options:
  • Link
    Copy

  Posted 27 December 2018, 11:58 am EST

  any news ?

• 

  mark

  • Post Options:
  • Link
    Copy

  Posted 10 April 2019, 4:43 pm EST

  Have you guys really not fixed this after almost two years? Honestly, if you can’t do the most basic optimization for Angular, you shouldn’t be selling an Angular version of your components.