Grid View Bug when allow auto add row and allow header selection is enabled

Grid View Bug when allow auto add row and allow header selection is enabled

Posted by: jgalera on 9 January 2019, 2:26 am EST

• 

  jgalera

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 9 January 2019, 2:26 am EST - Updated 29 September 2022, 5:50 am EST

  This bug was found and confirmed on the spread.views demo page. https://demos.componentone.com/Spread/JS/ViewsDemo/#/demos/AutoAddRow
  
  The Demo Example for the Auto Add Row feature does not include header Selection.
  
  Adding the following code to the demo code enables header Selection

  allowHeaderSelect: true
  

  Once the header Selection and auto add row are enabled, hover your cursor over the last row which is the auto added row with the header ‘*’ causes a console error.

  

  2557×333 37.7 KB

• 

  reeva.dhingra

  

  • Post Options:
  • Link
    Copy

  Posted 9 January 2019, 9:05 pm EST

  Hello,

  I couldn’t replicate the issue with the latest build of Spread.Views which is version 12.0.5.

  Hence, please check your case again the latest build which can be downloaded from this location:-
  
  https://www.grapecity.com/en/download/spreadjs

  Hope it helps. Please share your further observations on the same.

  Thanks,
  
  Reeva

• 

  jgalera

  • Post Options:
  • Link
    Copy

  Posted 22 January 2019, 6:07 am EST

  Hello,

  This issue is still currently reproducible in the given link above following the given steps. is the demo website running on the latest 12.0.5 version?

• 

  reeva.dhingra

  

  • Post Options:
  • Link
    Copy

  Posted 22 January 2019, 3:31 pm EST

  Hello,

  We could replicate the issue in Chrome browser with your steps. Hence, we have escalated the same to the concerned team for further investigation.

  Tracking id for your issue is #269406

  We will update you as soon as we hear anything from our concerned team.

  Thanks,
  
  Reeva

• 

  reeva.dhingra

  

  • Post Options:
  • Link
    Copy

  Posted 22 January 2019, 8:56 pm EST

  Hello,

  our developers have fixed your issue and it will be out in next release. We will keep you updated about the new build release.

  Thanks,
  
  Reeva