Steps to reproduce
Our PWA frequently exhibits poor performance in Edge, due to what we suspect is poor layout performance. Here’s one example:
- Open https://editor.construct.net/#open=ghost-shooter-tut
- Select Menu -> Project -> Close project
It takes about a second to respond. A profile shows this includes ~400ms of layout. Both Firefox and Chrome respond immediately.
Layout performance is a persistent problem with our PWA - it seems OK now in Chrome and Firefox, but Edge seems to show up the worst problems. I’ve blogged about this problem here: https://www.scirra.com/blog/ashley/35/layout-is-the-next-frontier-of-web-app-performance
We’d like to publish our PWA as a Windows Store app, but since it’s forced to use the Edge browser engine which has the worst performance characteristic in our PWA, we may have second thoughts.
Comments and activity
Click and drag the “Game Over!” text to the right, until the view starts scrolling.
The scrolling is janky. According to a performance profile, this is because it’s regularly doing ~50ms of layout (on an i7-6700K @ 4 GHz) to update the mouse position in the status bar or the position in the properties bar. Again, this is not a significant problem in other browsers, only Edge.
We use CSS containment everywhere we can, so adding support for that should solve this problem, since it will isolate layout work to just the minimal areas that need it.
- Microsoft Edge Team
Changed Assigned To to “Bogdan B.”
Changed Status to “Confirmed”