Bug 209733

Summary:

[iPadOS] Regression: Scrolling and Toolbar lags in Safari

Product:

WebKit

Reporter:

Mehmet <mehmet.sahin>

Component:

Scrolling

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Normal

CC:

simon.fraser, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

Safari 13

Hardware:

iPhone / iPad

OS:

iOS 13

Attachments:

Description	Flags
Video of the Address Bar flicker	none

Description Mehmet 2020-03-30 04:45:35 PDT

iPadOS 13.4
iPad Pro ML3K2FD/A
Safari for iPadOS

Dear Webkit-Team,

I noticed, that Scrolling in Safari for iPadOS lags on my iPad Pro ML3K2FD/A. I noticed this first, because the Toolbar flickers, when it changes from collapsed to uncollapsed state.

Steps to reproduce:

1.) Visit a page
2.) Scroll to the end of the page (Toolbar is still collapsed)
3.) Now swipe just a little bit very short and fast up so that the Toolbar uncollapsed and you scroll a little bit up.

Actual Result: The Toolbar (Address Bar and Tab Bar) flickers and the scrolling lags.

I wanted to take a screencast via the build-in recorder. But when the recorder is on, then the issue goes away?! Not sure, but it seems that the iPad runs in a lower framerate or in a low-power mode, so that the scrolling issue appears. But when the screenrecorder is on and the ipad uses (maybe) more power, then scrolling works perfectly and there is no issue with the Toolbar.

I hope this helps or maybe this is already a known issue. Otherwise I can record a screencast with the phone and share it here then.

Just let me know it.

Thanks for your great work and kind regards
Mehmet

Comment 1 Mehmet 2020-03-30 06:23:27 PDT

Created attachment 394910 [details]
Video of the Address Bar flicker

Please find attached a video of the flicker. It is easier to reproduce, when the Bookmarks List is enabled on the left side like in the video.

Comment 2 Radar WebKit Bug Importer 2020-03-30 13:46:43 PDT

<rdar://problem/61071184>

Comment 3 Mehmet 2023-05-30 11:56:47 PDT

Looks this is no longer an issue. Please feel free to close this bug report. Thanks :)