Bug 38810

Summary: Massive slow down with large CSS tables
Product: WebKit Reporter: Rene Trost <r.trost>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, jchaffraix, scheglov
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac (Intel)   
OS: OS X 10.6   
URL: http://downloads.syncbyte.com/table_test.html
Attachments:
Description Flags
Large Table with CSS (~2.1MB) none

Rene Trost
Reported 2010-05-09 00:16:27 PDT
Large HTML tables with CSS styles massively slowing down the browser. I've created a test-case with 15.000 rows for better comparison. While Firefox and Opera stay very responsive, all WebKit based browsers become extremely sluggish and slow. Within a Web-App that makes heavy use of JavaScript, this becomes an issue with much smaller tables already. In the test-case, I've removed all other page elements, JavaScripts and other CSS styles, because it would almost stall the browser if I've left them in. This problem only shows up with CSS tables.
Attachments
Large Table with CSS (~2.1MB) (45 bytes, text/plain)
2010-05-09 00:20 PDT, Rene Trost 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Rene Trost
Comment 1 2010-05-09 00:20:33 PDT
Created attachment 55491 [details] Large Table with CSS (~2.1MB) Large tables with CSS causing massive performance decrease
Julien Chaffraix
Comment 2 2011-08-29 17:49:24 PDT
Removing "border-collapse: border" leads to better performance. This is caused by us not caching the border information.
Rene Trost
Comment 3 2011-08-29 21:08:32 PDT
(In reply to comment #2) > Removing "border-collapse: border" leads to better performance. This is caused by us not caching the border information. Thanks! That's a solution I can work with!
Julien Chaffraix
Comment 4 2011-09-07 17:45:56 PDT
See bug 64546 for optimizing border-collapse performance.
Brent Fulgham
Comment 5 2022-07-01 17:02:17 PDT
The test case is no longer available. Given that Bug 64546 resolved the border-collapse issue, which seemed to be the culprit, closing this as well.
Note You need to log in before you can comment on or make changes to this bug.