When scrolling the Trac changeset page at <http://trac.webkit.org/changeset/66679> white one pixel horizontal lines appear in the green portions of the page when I pause and then resume scrolling. * STEPS TO REPRODUCE 1. Load <http://trac.webkit.org/changeset/66679>. 2. Scroll about a third of the way down the page so that the top of your window is half way through the added ChangeLog entry. 3. Scroll down a few lines, then pause for a second, and scroll back up slowly. * RESULT A white gap appears between each table row as you scroll up. * REGRESSION I bisected and tracked this down to r65539. <rdar://problem/8388281>
<http://trac.webkit.org/changeset/65539> was the change that introduced this.
I am seeing the issue. Will look into it. Thanks.
I have a fix locally. I just have to produce a layout test for it, and then I'll submit a patch. The issue is that the test cases I used to improve dirty cell selection had the border-collapse property set to collapse. In the case where border-collapse is separate, there is an off by one error that occasionally prevents dirty borders from repainting.
Created attachment 67238 [details] Patch
Created attachment 67474 [details] Patch
Comment on attachment 67474 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=67474&action=prettypatch > LayoutTests/fast/table/simple_paint_separate_borders.html:24 > + divbug.style.visibility = "hidden"; > + if (window.layoutTestController) { > + window.layoutTestController.notifyDone(); > + } > + } > + </script> > +</head> > + <body onload="setTimeout('repaintCell()', 1000)"> > + <div id="bug" style="position: absolute; left: 121px; top: 121px; width: 61px; height: 61px; background-color: red;"></div> I’m surprised that this technique works to test repainting behavior, since DumpRenderTree is supposed to invalidate everything by default. Anyway, even if it works, it appears to take a full second. You should use the standard mechanism for repaint tests instead (see LayoutTests/fast/repaint/resources/repaint.js).
Created attachment 67699 [details] Patch Updated layout tests according to Mitz' comments.
Comment on attachment 67699 [details] Patch The expected image for the new test doesn’t look right—it looks like the entire view repainted. You also changed an existing test but I don’t see new expected results.
Created attachment 69258 [details] Patch Fixed expectation pngs and minor tweaking of tests.
Comment on attachment 69258 [details] Patch Rejecting patch 69258 from commit-queue. Failed to run "['./WebKitTools/Scripts/webkit-patch', '--status-host=queues.webkit.org', 'apply-attachment', '--force-clean', '--non-interactive', '--quiet', 69258]" exit_code: 2 Cleaning working directory Updating working directory Logging in as commit-queue@webkit.org... Fetching: https://bugs.webkit.org/attachment.cgi?id=69258&action=edit Fetching: https://bugs.webkit.org/show_bug.cgi?id=45131&ctype=xml Processing 1 patch from 1 bug. Processing patch 69258 from bug 45131. Failed to run "[u'/Users/abarth/git/webkit-queue/WebKitTools/Scripts/svn-apply', u'--reviewer', u'Darin Adler', u'--force']" exit_code: 9 Full output: http://queues.webkit.org/results/4156031
Comment on attachment 69258 [details] Patch Rejecting patch 69258 from commit-queue. fsamuel@chromium.org does not have committer permissions according to http://trac.webkit.org/browser/trunk/WebKitTools/Scripts/webkitpy/common/config/committers.py. - If you do not have committer rights please read http://webkit.org/coding/contributing.html for instructions on how to use bugzilla flags. - If you have committer rights please correct the error in WebKitTools/Scripts/webkitpy/common/config/committers.py by adding yourself to the file (no review needed). The commit-queue restarts itself every 2 hours. After restart the commit-queue will correctly respect your committer rights.
It looks like the patch fails to apply. Sorry it's missing some output, we're fixing that.
(In reply to comment #12) > It looks like the patch fails to apply. Sorry it's missing some output, we're fixing that. Is there something I can do?
Yes, you need to post a patch which applies to tip of tree. :)
Created attachment 69862 [details] Patch
Committed r69161: <http://trac.webkit.org/changeset/69161>
*** Bug 47162 has been marked as a duplicate of this bug. ***