[Webkit-unassigned] [Bug 101522] New: Web Inspector: Indentify high-cost CSS declarations
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Nov 7 16:48:30 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=101522
Summary: Web Inspector: Indentify high-cost CSS declarations
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: paulirish at chromium.org
CC: keishi at webkit.org, pmuellr at yahoo.com,
pfeldman at chromium.org, yurys at chromium.org,
apavlov at chromium.org, loislo at chromium.org,
vsevik at chromium.org,
web-inspector-bugs at googlegroups.com
In the lifetime of an app, costly style rules can affect both transition/scroll FPS and application performance.
The costs will manifest as extra time spent in style recalc, reflow, paint, compositing.
Right now, there is no strong way to attribute the long bars in Timeline back to authored CSS rules, though I feel that delivers the most insight to the user.
I wanted to open up this ticket to discuss and track any progress on this front.
Some ideas I've heard so far:
* rendering performance heatmap
* element paint cost profile report
* zooming into Timeline bars for RenderTree breakdown
--
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