[Webkit-unassigned] [Bug 66184] New: Table border-collapse and transparency performance issues
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sat Aug 13 02:15:14 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=66184
Summary: Table border-collapse and transparency performance
issues
Product: WebKit
Version: 528+ (Nightly build)
Platform: Macintosh
URL: http://chadvonnau.com/projects/web/examples/webkit-tab
le-bug/bordercollapse.html
OS/Version: Mac OS X 10.6
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Tables
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: chadwhee at yahoo.com
I've made some examples to demonstrate some performance bugs with table rendering.
These examples are the same content with different styling:
1) Normal scrolling. Solid borders and border-collapse:separate
http://chadvonnau.com/projects/web/examples/webkit-table-bug/index.html
2) Slow scrolling. Solid borders and border-collapse:collapse
http://chadvonnau.com/projects/web/examples/webkit-table-bug/bordercollapse.html
3) Very slow scrolling and beach ball of death.
Semi-transparent RGBA borders and border-collapse:separate
http://chadvonnau.com/projects/web/examples/webkit-table-bug/rgbaborders.html
I'm testing with Safari 5.1 and OS X 10.6.8 (+update) on my Late 2006 MacBook Pro.
Firefox 4 sees roughly equal performance on on all of those examples.
Safari 5.0 and earlier sees about the same performance on each example.
Chrome 13.0.7 has similar performance issues with these examples.
I reported what I believe to be the same issue to Google several months back. Here's my bug report with google:
http://code.google.com/p/chromium/issues/detail?id=68215
Perhaps these issues may be coming from webkit code that Google has been using for a few months but only made it into Safari in 5.1.
Here is another page that exhibits performance problems because of border-collapse:collapse
http://panlex.org/u
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list