Appending rows to a table in Edge is really slow (layout issues)

Fixed Issue #10350230

Details

Created
Dec 30, 2016
Privacy
This issue is public.
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Edge really lags other browsers when it comes to appending rows to a table

https://jsbin.com/duqemi/edit?html,js,console,output

Edge: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393”
“268ms, loadRows: 1000 rows, concat: arr”
“269ms, loadRows: 1000 rows, concat: str”
“1657ms, loadRows: 5000 rows, concat: arr”
“1667ms, loadRows: 5000 rows, concat: str”

Chrome: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36”
“58ms, loadRows: 1000 rows, concat: arr”
“54ms, loadRows: 1000 rows, concat: str”
“231ms, loadRows: 5000 rows, concat: arr”
“219ms, loadRows: 5000 rows, concat: str”

Firefox: “Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0”
“95ms, loadRows: 1000 rows, concat: arr”
“84ms, loadRows: 1000 rows, concat: str”
“322ms, loadRows: 5000 rows, concat: arr”
“325ms, loadRows: 5000 rows, concat: str”

IE 11 “Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; rv:11.0) like Gecko”
“618ms, loadRows: 1000 rows, concat: arr”
“490ms, loadRows: 1000 rows, concat: str”
“2100ms, loadRows: 5000 rows, concat: arr”
“1834ms, loadRows: 5000 rows, concat: str”

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Status to “Confirmed”

      Changed Title from “Appending rows to a table in Edge is really slow” to “Appending rows to a table in Edge is really slow (layout issues)”

      Changed Status from “Confirmed”

      Changed Assigned To to “Bogdan B.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Won’t fix”

      Changed Status from “Won’t fix” to “Fixed”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 16299 and is available in our current public stable build.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in