Bug 132158 - ScrollingCoordinator is unaware of topContentInset
Summary: ScrollingCoordinator is unaware of topContentInset
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P1 Blocker
Assignee: Brent Fulgham
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2014-04-24 17:29 PDT by Brent Fulgham
Modified: 2014-04-25 08:28 PDT (History)
10 users (show)

See Also:


Attachments
Patch (9.07 KB, patch)
2014-04-24 18:22 PDT, Brent Fulgham
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Brent Fulgham 2014-04-24 17:29:15 PDT
The calculation of non-fast-scrollable regions does not currently take the topContentOffset into account. Consequently, the logic that decides whether to stay on the scrolling thread, or drop down to an individual page element, can make the wrong choice. This is especially true for small scrollable regions (such as <select> elements), where the topContentInset may be quite close to the size of the scrollable element itself.
Comment 1 Brent Fulgham 2014-04-24 17:30:20 PDT
<rdar://problem/16706152>
Comment 2 Brent Fulgham 2014-04-24 18:22:13 PDT
Created attachment 230126 [details]
Patch
Comment 3 Tim Horton 2014-04-24 18:25:13 PDT
Comment on attachment 230126 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=230126&action=review

> LayoutTests/platform/mac/fast/scrolling/scroll-select-bottom-test.html:52
> +    //debug("Page before: " + pageScrollPositionBefore + ", select before: " + selectScrollPositionBefore);
> +    //debug("Page after:  " + pageScrollPositionAfter + ", select after: " + selectScrollPositionAfter);

???
Comment 4 Brent Fulgham 2014-04-24 19:08:33 PDT
Comment on attachment 230126 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=230126&action=review

>> LayoutTests/platform/mac/fast/scrolling/scroll-select-bottom-test.html:52
>> +    //debug("Page after:  " + pageScrollPositionAfter + ", select after: " + selectScrollPositionAfter);
> 
> ???

WK1 and WK2 sometimes produce different values here. Rather than baseline both, we comment these out. It's useful to uncommercial them while debugging.
Comment 5 Brent Fulgham 2014-04-24 19:09:20 PDT
(In reply to comment #4)
> (From update of attachment 230126 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=230126&action=review
> 
> >> LayoutTests/platform/mac/fast/scrolling/scroll-select-bottom-test.html:52
> >> +    //debug("Page after:  " + pageScrollPositionAfter + ", select after: " + selectScrollPositionAfter);
> > 
> > ???
> 
> WK1 and WK2 sometimes produce different values here. Rather than baseline both, we comment these out. It's useful to uncommercial them while debugging.

And by uncommercial, I of course mean uncomment them.
Comment 6 WebKit Commit Bot 2014-04-25 08:28:23 PDT
Comment on attachment 230126 [details]
Patch

Clearing flags on attachment: 230126

Committed r167807: <http://trac.webkit.org/changeset/167807>
Comment 7 WebKit Commit Bot 2014-04-25 08:28:27 PDT
All reviewed patches have been landed.  Closing bug.