Bug 201018
| Summary: | Migrate from m_layoutTimer to scheduled rendering updates | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bfulgham, koivisto, rniwa, sabouhallawa, simon.fraser, zalan |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=201019 https://bugs.webkit.org/show_bug.cgi?id=208780 |
||
| Bug Depends on: | |||
| Bug Blocks: | 202843 | ||
Simon Fraser (smfr)
Now that we have the rendering update mechanism (RenderingUpdateScheduler), we should remove m_layoutTimer and just call scheduleRenderingUpdate().
I see extra layouts in traces from the layout timer, which never make it to the screen because something else dirties layout before the next update.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
zalan
(In reply to Simon Fraser (smfr) from comment #0)
> Now that we have the rendering update mechanism (RenderingUpdateScheduler),
> we should remove m_layoutTimer and just call scheduleRenderingUpdate().
>
> I see extra layouts in traces from the layout timer, which never make it to
> the screen because something else dirties layout before the next update.
This is great! (though having multiple layouts within the same update does not necessarily mean redundant work.)