Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4084

Tree scroll position is not properly maintained (Firefox/Chrome)

    Details

    • Release notes required:
      Yes
    • Sprint:
      Saigon 79, Saigon 80, Saigon 81
    • Story Points:
      8
    • Magnolia Release:
      5.3.18, 5.4.11, 5.5.2

      Description

      Trees have become less usable in Firefox "lately"—especially there seems to be an increase of "jumping" issues.

      When using inplace-editing below the fold (in config-app)

      • hitting ENTER on property names or property values abnormally centers the selected row [1]
      • hitting ENTER on a node name scrolls back to the top
      • hitting ESC scrolls back to the top
      • hitting TAB doesn't jump at all

      When using the context menu below the fold (via Sang Ngo Huu, thanks for reporting)

      • Right-clicking an unselected row abnormally centers that row [1]
        • Clicking aside to close it scrolls back to the top
      • Right-clicking a selected row doesn't jump at all
      notes
      • Chrome now doesn't suffer the same symptoms
      • I could reproduce it also on 5.4.6, so it is well possibly caused by a change in recent Firefox versions, rather than inside the UI framework or Vaadin.

      [1] I suspect the RowScroller to come into play here somehow


      Update 2016.12.28

      Chrome now suffers as well from scrolling back to top, albeit slightly differently:

      • hitting ENTER or ESC in inline-editing (TAB also doesn't jump)

      upon any "indirect selection changes",

      • e.g. adding nodes, properties (unlike FF)
      • Right-clicking an unselected node (unlike FF's "centering effect")

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hieu.nguyen Hieu Nguyen Duc
                Reporter:
                mgeljic Mikaël Geljić
              • Votes:
                5 Vote for this issue
                Watchers:
                15 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response:

                  Time Tracking

                  Estimated:
                  Original Estimate - 6d
                  6d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 2d 5h Time Not Required
                  2d 5h