Bug 219594

Summary: [GTK][WPE] Overflow/iframe scrolling with async scrolling enabled sometimes doesn't work
Product: WebKit Reporter: Chris Lord <clord>
Component: ScrollingAssignee: Chris Lord <clord>
Status: RESOLVED FIXED    
Severity: Normal CC: cgarcia, cmarcelo, ews-watchlist, fred.wang, jamesr, koivisto, luiz, simon.fraser, tonikitoo, webkit-bug-importer, zan
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=214179
Attachments:
Description Flags
Patch
none
Patch none

Chris Lord
Reported 2020-12-07 02:17:59 PST
I dealt with this in bug 214179, but it turns out my implementation was flawed. It's possible for a descendent layer to contain a point that its ancestor doesn't, and this occurs very commonly with iframes (but not at all commonly with overflow scrolling). The Mac backend deals with this by just not doing any bounds checking, so we should do the same with nicosia.
Attachments
Patch (3.75 KB, patch)
2020-12-07 02:28 PST, Chris Lord 		no flags
DetailsFormatted DiffDiff
Patch (3.75 KB, patch)
2020-12-07 02:49 PST, Chris Lord 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Chris Lord
Comment 1 2020-12-07 02:28:38 PST
Created attachment 415542 [details] Patch
Chris Lord
Comment 2 2020-12-07 02:49:44 PST
Created attachment 415544 [details] Patch
EWS
Comment 3 2020-12-07 03:30:03 PST
Committed r270501: <https://trac.webkit.org/changeset/270501> All reviewed patches have been landed. Closing bug and clearing flags on attachment 415544 [details].
Radar WebKit Bug Importer
Comment 4 2020-12-07 03:31:26 PST
<rdar://problem/72042253>
Note You need to log in before you can comment on or make changes to this bug.