Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Poor Performace using the Edge Browser with Virtual Scrolling

See original GitHub issue

I’m submitting a … (check one with “x”)

[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior Chrome Browser - Scrolls like “butter” and fills in rows before visually displayed on demo page Edge Browser - When scrolling fast, takes approximately 500ms to populate the page with rows. It shows only whitespace indicating that it’s taking much longer to render rows.

Expected behavior Scrolls like butter as demoed using the Chrome browser.

Reproduction of the problem Go to the demo page, and select Basic\10k Rows using the Edge browser on the Anniversary Update version of Windows 10 and scroll very rapidly. Clicking and dragging the side scrollbar makes this performance issue obvious.

What is the motivation / use case for changing the behavior? Improve the user experience.

Please tell us about your environment: Windows 10 Anniversary Update, Microsoft EdgeHTML 14.14393, Surface Book i7

Table version: 0.7.x N/A
Angular version: 2.0.x N/A
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ] Edge
Language: [all | TypeScript X.X | ES6/7 | ES5] N/A

Closing thoughts to this matter I remember hearing somewhere that the Edge browser pre-compiles the webpage and JavaScript prior to displaying the content instead of interpreting the content directly. Might it be possible that the virtual DOM is being recompiled each scroll event causing severe performance degradation? I’m not sure if this is directly related to the project or is a unique use-case that is being mishandled by the browser itself and should be reported directly to Microsoft.