Bug 71475 - REGRESSION: Scrolling doesn't update content area in nested overflow-y:auto divs
Summary: REGRESSION: Scrolling doesn't update content area in nested overflow-y:auto divs
Status: RESOLVED DUPLICATE of bug 71550
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P1 Normal
Assignee: Julien Chaffraix
URL:
Keywords: Regression
Depends on:
Blocks:
 
Reported: 2011-11-03 08:20 PDT by asvitkine
Modified: 2011-11-07 16:56 PST (History)
3 users (show)

See Also:

Attachments
Test case (1.21 KB, text/html)
2011-11-03 08:20 PDT, asvitkine 		no flags Details
WIP change: undertested, likely too much recomputations, will think it over on Monday. (11.42 KB, patch)
2011-11-04 21:22 PDT, Julien Chaffraix 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description asvitkine 2011-11-03 08:20:18 PDT 
Attached reduced testcase (from a PHPBB forum page) has two fixed height divs both with scroll bars. The inner div's content doesn't update when you scroll it via the inner scroll bar.

According to Chromium's bisect-builds.py, this regressed between WebKit revisions 93556 and 93643.
Comment 1 asvitkine 2011-11-03 08:20:47 PDT 
Created attachment 113496 [details]
Test case
Comment 4 asvitkine 2011-11-03 08:28:14 PDT 
Suspecting it might be this change:

"Reduce the amount of RenderLayer rectangles' update when scrolling"
http://trac.webkit.org/changeset/93614/trunk
Comment 5 Julien Chaffraix 2011-11-04 12:08:41 PDT 
Confirmed. Taking over as this is a bad regression.
Comment 6 Julien Chaffraix 2011-11-04 21:22:49 PDT 
Created attachment 113750 [details]
WIP change: undertested, likely too much recomputations, will think it over on Monday.
Comment 7 Julien Chaffraix 2011-11-07 16:56:38 PST 
webkit-patch attached the patch to the wrong bug (should have gone to bug 71550). Merging the 2 bugs together.

*** This bug has been marked as a duplicate of bug 71550 ***