Bug 214627 - Scrolling tesla.com on iPad is not smooth
Summary: Scrolling tesla.com on iPad is not smooth
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Scrolling (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Simon Fraser (smfr)
URL:
Keywords: InRadar
: 215254 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-07-21 22:04 PDT by Simon Fraser (smfr)
Modified: 2020-08-16 18:34 PDT (History)
13 users (show)

See Also:


Attachments
Patch (35.57 KB, patch)
2020-07-21 22:09 PDT, Simon Fraser (smfr)
thorton: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 2020-07-21 22:04:09 PDT
Scrolling tesla.com on iPad is not smooth
Comment 1 Simon Fraser (smfr) 2020-07-21 22:09:02 PDT
Created attachment 404900 [details]
Patch
Comment 2 Simon Fraser (smfr) 2020-07-21 22:09:05 PDT
<rdar://problem/65568979>
Comment 3 Tim Horton 2020-07-22 09:51:37 PDT
Comment on attachment 404900 [details]
Patch

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

Sbould make sure that a page that goes into the page cache with an active scroll comes out of it without one, probably?

> Source/WebKit/Shared/RemoteLayerTree/RemoteScrollingUIState.h:50
> +    RemoteScrollingUIState() = default;

Isn't this line needless?
Comment 4 Tim Horton 2020-07-22 09:52:03 PDT
(or the process-swappy-cache, which ... might be the same?)
Comment 5 Chris Dumez 2020-07-22 10:04:02 PDT
(In reply to Tim Horton from comment #4)
> (or the process-swappy-cache, which ... might be the same?)

It is called back/forward cache now and is the same whether you proses-swap or not :)
Comment 6 Chris Dumez 2020-07-22 10:06:51 PDT
Cc'ing Keith because he cares :)
Comment 7 Simon Fraser (smfr) 2020-07-22 10:48:54 PDT
https://trac.webkit.org/changeset/264704/webkit
Comment 8 Simon Fraser (smfr) 2020-08-13 21:11:16 PDT
*** Bug 215254 has been marked as a duplicate of this bug. ***