Bug 123753
| Summary: | Consider removing flushCompositingStateForThisFrame() from FrameView::paintContents | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
| Component: | Layout and Rendering | Assignee: | Simon Fraser (smfr) <simon.fraser> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | simon.fraser, thorton |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Simon Fraser (smfr)
A call to flushCompositingStateForThisFrame() was added to FrameView::paintContents() in http://trac.webkit.org/changeset/46645 to ensure that compositing layers are flushed in sync with painting.
However, this model only makes sense in the non layer-backed WK1 code path (where painting is going to the window, and layers are composited separately). If everything is CA-rendered, (iOS, or WK2), then this call is a waste of time. We won't hit this for WK2 though.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Simon Fraser (smfr)
Fixing this via 130627.
*** This bug has been marked as a duplicate of bug 130627 ***