Wj-flex-grid rendering issue

Posted by: kun.leeing on 24 June 2019, 12:55 pm EST

    • Post Options:
    • Link

    Posted 24 June 2019, 12:55 pm EST

    Hi there,

    We are putting several wj-flex-grid with a dynamic columns to the separate pages in a ngtabs . For the first time of loading and rendering, it sometimes shows a rendering issue as it is not showing everything correctly, just a few cells which is part of the records. Then I put a refresh button onto the page for testing reload the data and refresh the grid. Then almost every time it could not be rendered correctly. Sometimes, one got the issue , sometimes both.

    Then I checked html generated, I found an inconsistent in wj-flex-grid-column and the <div wj-part above it. For example,

    It has the dom

    <wj-flex-grid-column _ngcontent-c25="" wj-directive-id="4" ng-reflect-binding="TestName" ng-reflect-header="Test Name" ng-reflect-width="200" ng-reflect-allow-resizing="false" ng-reflect-visible="true" style="display: none;"><div></div></wj-flex-grid-column>
    

    But there is no

    <div class="wj-row"><div tabindex="-1" class="wj-cell wj-header d-flex align-items-end" style="left: 0px; top: 0px; width: 220px; height: 130px; z-index: 1;"><span _ngcontent-c25="">Test Data</span></div> 
    

    corresponding to it.

    Could someone let me know the reason of this effect?

    Thanks in advance.

  • Posted 24 June 2019, 1:01 pm EST

    Sorry, forgot one thing. on the ngb-tabset, I put [destroyOnHide]=“false” for performance consideration. If turn it to true, there is no this issue.

  • Posted 24 June 2019, 9:59 pm EST

    We are sorry but we were not able to replicate the issue at our end. Please refer to the sample below which we used to replicate the issue:

    https://stackblitz.com/edit/angular-bjpjgx

    Could you please tell whether we are missing something? You may also update the provided sample or provide with your own sample that replicates the issue.

  • Posted 25 June 2019, 7:25 pm EST

    Hi abhishek,

    Thanks for replying and your sample project. Because of that, it is fixed after upgrading wijmo from 5.20183.568 to 5.20191.615.

    Cheers

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels