Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 6.4.9, 22.08.7, 23.02.3
    • 23.08.4
    • maxgui
    • None
    • MXS-SPRINT-191, MXS-SPRINT-192

    Description

      The result data table supports only vertical virtual scroll, if the resultset has a large number of columns, the memory consumption would increase significantly and cause laggy issues.
      The virtual scroll should automatically work in both directions, vertical and horizontal.
      At the moment, the customized virtual scroll table component is built on top of vuetify v-virtual-scroll which supports only vertical direction.

      https://nhn.github.io/tui.grid/latest/ is a good candidate to replace the customized component.
      Example: https://codesandbox.io/s/tui-grid-vrtmjj
      However, building a virtual scroll component from scratch seems to be a better idea instead of relying on 3rd party library.

      Attachments

        Issue Links

          Activity

            thien.ly Thien Ly added a comment -

            Adding virtualization support for both axes is nice but not trivial.
            Hence, the current result data table has been optimized to handle many columns.
            Only the first 50 columns will be rendered by default to prevent laggy scrolling.

            thien.ly Thien Ly added a comment - Adding virtualization support for both axes is nice but not trivial. Hence, the current result data table has been optimized to handle many columns. Only the first 50 columns will be rendered by default to prevent laggy scrolling.

            People

              thien.ly Thien Ly
              thien.ly Thien Ly
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.