Bug 8535

Summary: Incorrect cyan debug mode painting
Product: WebKit Reporter: Alexey Proskuryakov <ap>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: ddkilzer, ggaren, ian, robert
Priority: P3 Keywords: HasReduction
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
test case none

Alexey Proskuryakov
Reported 2006-04-22 08:36:14 PDT
The attached test case paints incorrectly in debug builds.
Attachments
test case (189 bytes, text/html)
2006-04-22 08:36 PDT, Alexey Proskuryakov 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2006-04-22 08:36:34 PDT
Created attachment 7910 [details] test case
Alexey Proskuryakov
Comment 2 2006-04-22 08:40:38 PDT
From [WebFrameView drawRect:]: #ifndef NDEBUG if ([[self _scrollView] drawsBackground]) { [[NSColor cyanColor] set]; NSRectFill(rect); } #endif Since RenderWidget::paint() calls paintBoxDecorations() first, and m_widget->paint() later, this paints over an already painted background. Removing this block has fixed the problem in Safari, but DumpRenderTree didn't paint the IFRAME background at all then. I am not sure how much related these problems are, though.
Alexey Proskuryakov
Comment 3 2006-07-18 12:06:09 PDT
*** Bug 9982 has been marked as a duplicate of this bug. ***
David Kilzer (:ddkilzer)
Comment 4 2006-07-18 12:21:42 PDT
It's really interesting to see what gets repainted when various actions are taken, though!
Alexey Proskuryakov
Comment 5 2006-12-10 21:35:53 PST
*** Bug 11799 has been marked as a duplicate of this bug. ***
Robert Hogan
Comment 6 2013-06-04 11:05:31 PDT
This works fine for me on a debug build of DumpRenderTree for the Qt port and a debug build of QtTestBrowser. OK to close?
Alexey Proskuryakov
Comment 7 2013-06-04 11:08:42 PDT
This code is Mac specific, so testing Qt is not necessarily relevant. However, I cannot reproduce on Mac either, and haven't seen such cyan painting in years.
Note You need to log in before you can comment on or make changes to this bug.