Created attachment 48380 [details] [review] Complete fix to intersect_with_boxes(). The old code forgot to dereference the boxes pointer. That commit only partially fixes things; the code still fails to look at all of the num_boxes boxes, but rather looks at the 0th box num_boxes times. W/o this further fix seamonkey frequently fails to update its window until an Expose event shows up. Or only updates a tiny chunk of the window. [bz Version field should, of course, be master....]
Created attachment 48381 [details] [review] Another possible patch to fix the issue Sorry for the delay (I read your message in the mailing list, but I was busy tacking other issues) I'd like the attached fix better, because it avoids the initialization (asserting that it can actually do that) and walks the boxes in order, which is less surprising when reading the code (at least for me, because it's easier to see that it iterates exactly on everything, without having to worry about the first/last element).
For attachment #48381 [details] [review]: Reviewed-by: James Cloos <cloos@jhcloos.com> Testing now.
For attachment #48381 [details] [review]: with the obvious addition of declaring int i: Tested-by: James Cloos <cloos@jhcloos.com> It works as well as my patch does.
The second attachment has been pushed to master: commit a447e949799000760835beeafd2d45c76580fb9e Author: Andrea Canciani <ranma42@gmail.com> Date: Fri Jun 24 15:52:24 2011 +0200 clip: Fix boxes extents computation in intersect_with_boxes The extents of the boxes were being computed by taking into account just the first box instead of all of them. Based on a patch by James Cloos. Fixes clip-disjoint, clip-stroke-unbounded, clip-fill-nz-unbounded, clip-fill-eo-unbounded, clip-fill, clip-stroke, trap-clip. See https://bugs.freedesktop.org/show_bug.cgi?id=38641 Reviewed-by: James Cloos <cloos@jhcloos.com> Tested-by: James Cloos <cloos@jhcloos.com>
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.