Bug 203412 - [GTK][WPE] Cover area for sticky elements is not updated when async scrolling is enabled (default behavior)
Summary: [GTK][WPE] Cover area for sticky elements is not updated when async scrolling...
Status: RESOLVED DUPLICATE of bug 219776
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 202449
Blocks:
  Show dependency treegraph
 
Reported: 2019-10-25 07:38 PDT by Pablo Saavedra
Modified: 2021-01-13 01:40 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo Saavedra 2019-10-25 07:38:57 PDT
Scrolling inside of the sticky elements with fixed position is still not working fine for all the situations. For example: https://people.igalia.com/psaavedra/scroll.html.

In this example, the scroll inside the `div` element  is consistent but when you does a scroll in the body element it seems the fixed position element doesn't manage the offset correctly resulting in a displacement in the opposite direction of the scrolling action

The same doesn't happens disabling the async scrolling:

```
export WEBKIT_DISABLE_ASYNC_SCROLLING=OFF
```

Related to: https://bugs.webkit.org/show_bug.cgi?id=202449
Comment 1 Pablo Saavedra 2019-11-04 01:06:46 PST
The issue is much more likely to the drawn area for the sticky scrollable element not being extended as we reaching the end of the initial cover area for the generated tiles for this layer resulting in a blank rendered page as we are doing scrolling down over it.
Comment 2 Pablo Saavedra 2019-11-05 01:36:17 PST
There are another thing that it worth to mention here. The scrolling for the overflow scrollable element only works when the body element is not scrolled (position 0,0).
Comment 3 Chris Lord 2020-12-11 04:51:38 PST
I expect the bug would have been initially 'fixed' by bug 218974 and then hopefully will stay fixed after bug 219776. I'll look now and if it isn't, endeavour to fix it.
Comment 4 Chris Lord 2020-12-11 07:04:10 PST
Can confirm this works fine with bug 219776 applied.

*** This bug has been marked as a duplicate of bug 219776 ***
Comment 5 Pablo Saavedra 2021-01-13 01:40:56 PST
(In reply to Chris Lord from comment #4)
> Can confirm this works fine with bug 219776 applied.
> 
> *** This bug has been marked as a duplicate of bug 219776 ***

Nice!. Thanks for take care about this. Really cool to have this working in WPE at last.