|Summary:||Calls to WebCore::Document::mayCauseFlashOfUnstyledContent make frequently-run drawing methods slower|
|Product:||WebKit||Reporter:||Ian Henderson <ian>|
|Component:||WebCore Misc.||Assignee:||Nobody <webkit-unassigned>|
|Severity:||Normal||CC:||ap, ddkilzer, hyatt, morrita, psolanki, simon.fraser|
|Version:||528+ (Nightly build)|
|OS:||OS X 10.6|
Description Ian Henderson 2011-04-13 21:58:37 PDT
In https://bugs.webkit.org/show_bug.cgi?id=45640, we added a more complicated heuristic to determine whether drawing may cause a flash of unstyled content. The WebCore::Document::mayCauseFlashOfUnstyledContent method is called during every WebCore::RenderBlock::paintContents and WebCore::RenderLayer::paintLayer, both of which may be called many times on a complex page. The additional complexity adds measurable overhead to these methods.
Comment 1 Hajime Morrita 2011-04-14 09:59:27 PDT
Okay, I'll remove mayCauseFlashOfUnstyledContent() usage. I'd like to keep mayCauseFlashOfUnstyledContent() definition to possibly use it on browser's paint() side, instead of preventing repaint() as we are doing now.
Comment 3 Hajime Morrita 2011-04-15 17:29:59 PDT
I changed my mind to just roll it out.