Bug 101522
| Summary: | Web Inspector: Identify high-cost CSS declarations | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Paul Irish <paulirish> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | apavlov, bburg, divya, dtrebbien, glenn, graouts, janx, joepeck, keishi, loislo, pfeldman, pmuellr, timothy, vsevik, web-inspector-bugs, webkit-bug-importer, yurys |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Paul Irish
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/19106888>
Blaze Burg
Is CSS really a bottleneck anymore with the CSS JIT?
Timothy Hatcher
Nope. We removed the CSS profiler a while ago too.