Bug 27042

Summary: Incomplete painting of newly created floats
Product: WebKit Reporter: mitz
Component: Layout and RenderingAssignee: mitz
Status: RESOLVED FIXED    
Severity: Normal Keywords: InRadar
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch, including repaint tests simon.fraser: review+

mitz
Reported 2009-07-07 14:14:10 PDT
<rdar://problem/7010981> Floats of a newly created block can fail to paint correctly if the block’s initial position is not (0, 0) in the parent’s coordinate system. A newly created float that ends up at (0, 0) in its parent’s coordinate system can fail to paint correctly. While these are distinct issues, I discovered one while working on the other so I have a single patch for both, with two separate test cases. Patch forthcoming.
Attachments
Patch, including repaint tests (39.27 KB, patch)
2009-07-07 14:21 PDT, mitz
simon.fraser: review+
mitz
Comment 1 2009-07-07 14:21:12 PDT
Created attachment 32393 [details] Patch, including repaint tests
Simon Fraser (smfr)
Comment 2 2009-07-07 14:32:05 PDT
Comment on attachment 32393 [details] Patch, including repaint tests > + for (size_t i = 0; i < floatCount; ++i) { > + if (!floats[i].everHadLayout) { > + RenderBox* f = floats[i].object; > + if (!f->x() && !f->y() && f->checkForRepaintDuringLayout()) I have a preference for comparing with 0 for coordinates, but r=me
mitz
Comment 3 2009-07-07 14:36:50 PDT
Note You need to log in before you can comment on or make changes to this bug.